I am testing kde frameworks 5 in the kde overlay, and discovered that libkscreen-9999 does not compile due to: /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lxcb-xevie /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lxcb-xprint Looking at the 1.11 version of the ebuild, I see a patch that applies to prevent them from being built, which cause this whole issue. Maybe applying the patch to disable/enable them via use flag in order to allow stuff depending on it to compile? Reproducible: Always
Fix KDE framework 5 not to use those libs. The X.org server no longer supports them, the code was removed.
(In reply to Rémi Cardona from comment #1) > Fix KDE framework 5 not to use those libs. The X.org server no longer > supports them, the code was removed. The code is not removed, at least not in version 1.11, because simply removing the patch to disable them from being built makes them build thus it is there.
(In reply to David Carlos Manuelda from comment #2) > The code is not removed It is removed from the *server*. In other words, the xcb libraries will have nothing to talk to on the other end. The bottom line is still the same: the best solution is to remove support for libxcb-{xprint,xevie} from KDE framework 5. The features that rely on said support will *not* work anyway. Since there has been a community-wide effort to stop using xevie (xprint was never really used to begin with), we have no intention of bringing said support back in portage. Feel free to modify the ebuild in a local overlay until you figure out how to disable the offending code. The 1.11 ebuild is easily modified by removing the patch that disables xprint and xevie. For the -9999 ebuild in the overlay, you'll need to revert the patch. Good luck
