g++ X11Clipboard.cpp In file included from X11Clipboard.cpp:8: /var/tmp/portage/media-libs/lsp-plugins-1.1.5/work/lsp-plugins-lsp-plugins-1.1.5/include/ui/ws/x11/ws.h:24:14: fatal error: cairo-xlib.h: No such file or directory #include <cairo-xlib.h> ^~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_20190219-222146 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] pypy3 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-1.32.0 * emerge -qpvO media-libs/lsp-plugins [ebuild N ] media-libs/lsp-plugins-1.1.5 USE="lv2 -doc -jack -ladspa"
Created attachment 566270 [details] emerge-info.txt
Created attachment 566272 [details] emerge-history.txt
Created attachment 566274 [details] environment
Created attachment 566276 [details] etc.portage.tbz2
Created attachment 566278 [details] media-libs:lsp-plugins-1.1.5:20190224-012807.log
Created attachment 566280 [details] temp.tbz2
Can you show me your emerge -pv 'x11-libs/cairo' It's likely it's missing the X useflag.
(In reply to Matthew Thode ( prometheanfire ) from comment #7) > Can you show me your emerge -pv 'x11-libs/cairo' It's likely it's missing > the X useflag. Sure: tinderbox@mr-fox ~ $ scw run/17.0_20190219-222146 mr-fox ~ # emerge -pv x11-libs/cairo These are the packages that would be merged, in reverse order: Calculating dependencies .... . .... ..... done! [ebuild R ] x11-libs/cairo-1.16.0-r2::gentoo USE="glib svg -X (-aqua) -debug (-gles2) -opengl -static-libs -utils -valgrind -xcb" ABI_X86="(64) -32 (-x32)" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB mr-fox ~ # exit logout (BTW I'm curious if this info isn't in the atatched etc.portage.tbz2 ?)
ya, it needs X. It was probably in etc.portage.tbz2 gonna update the ebuild
forgot to mention the bug in the commit, but should be fixed now