from client_base.hxx:28, from client_base.cxx:10: compositor.hxx:18:30: fatal error: cairo/cairo-xlib.h: No such file or directory compilation terminated. make[2]: *** [Makefile:601: client_base.o] Error 1 make[2]: Leaving directory '/var/tmp/portage/x11-wm/page-1.9.7/work/page-1.9.7/src' ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-unstable_20170123-090431) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config --version: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: -----------------------------------------------------------------
Created attachment 461284 [details] emerge-info.txt
Created attachment 461286 [details] config.log
Created attachment 461288 [details] emerge-history.txt
Created attachment 461290 [details] environment
Created attachment 461292 [details] etc.portage.tbz2
Created attachment 461294 [details] x11-wm:page-1.9.7:20170124-213215.log
Thank you for the report, I will have a look Best regards
Hi Benoit, I noticed you've released 1.9.8. Does this version fix that bug? Please let me know and I'll bump the package ASAP.
It does. I didn't read your comments on the other bugs. It's a bit difficult to keep track of what's going on when posting updates all over the place. Feel free to close the other tickets as well. Thanks!
(In reply to Patrice Clement from comment #9) > It does. I didn't read your comments on the other bugs. It's a bit difficult > to keep track of what's going on when posting updates all over the place. > Feel free to close the other tickets as well. Thanks! @Patrice: Hello Patrice, No trouble here, Thanks for you commitment on gentoo ;) Best regards. @Toralf: Hello Toralf, Can you confirm that the version 1.9.8 fix this bug :) Best regards.
Version bumped to 1.9.8.
Let's close this bug. @Toralf: feel free to reopen if it doesn't fix the issue.