These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R *] dev-qt/qtopengl-5.9999:5/5.9999::qt USE="-debug -gles2 {-test}" 0 KiB [ebuild R *] dev-qt/qtprintsupport-5.9999:5/5.9999::qt USE="cups -debug -gles2 {-test}" 0 KiB XLib enabled. Mir client auto-detection... () Project ERROR: mirclient development package not found Mir client disabled. No QPA platform plugin enabled! If you really want to build without a QPA platform plugin you must pass -no-qpa-platform-guard to configure. Doing this will produce a Qt that can not run GUI applications. The dependencies needed for xcb to build are listed in src/plugins/platforms/xcb/README * ERROR: dev-qt/qtprintsupport-5.9999::qt failed (configure phase): * configure failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 3253: Called qt5-build_src_configure * environment, line 2854: Called qt5_base_configure * environment, line 2958: Called die * The specific snippet of code: * "${S}"/configure "${conf[@]}" || die "configure failed";
from http://code.qt.io/cgit/qt/qtbase.git/plain/configure?h=dev -no-xcb ............ Do not compile Xcb (X protocol C-language Binding) support. * -xcb ............... Compile Xcb support. -no-eglfs .......... Do not compile EGLFS (EGL Full Screen/Single Surface) support. * -eglfs ............. Compile EGLFS support. -no-directfb ....... Do not compile DirectFB support. * -directfb .......... Compile DirectFB support. -no-linuxfb ........ Do not compile Linux Framebuffer support. * -linuxfb ........... Compile Linux Framebuffer support. -no-kms ............ Do not compile KMS support. * -kms ............... Compile KMS support (Requires EGL). * -no-mirclient....... Do not compile Mir client support. -mirclient.......... Compile Mir client support. -qpa <name> ......... Sets the default QPA platform (e.g xcb, cocoa, windows). -xplatform target ... The target platform when cross-compiling.
For xcb I would suggest something like that: https://gitweb.gentoo.org/proj/qt.git/commit/?id=a606936208398a61e35dd4846926be872ce0b466
All dev-qt/qt*-5.9999 packages from Qt Base (Core, Gui, Widgets, Network, ...) fail now with the same message. USE flags have to be added for some configure options.
Mir isn't packaged in gentoo AFAICS, so I'll just change the eclass to always pass -no-mirclient
(In reply to Davide Pesavento from comment #4) > Mir isn't packaged in gentoo AFAICS, so I'll just change the eclass to > always pass -no-mirclient That would be great if the USE-flags for the QT packages were corrected and the eclass thing. Now this is a real show stopper for me as I can't get solved other KDE related bugs.
(In reply to jospezial from comment #5) > Now this is a real show stopper for me as I can't get solved other KDE > related bugs. well, why are you using the *live* version from an *overlay* that builds the upstream *dev* branch if you depend on it for other stuff then? You really can't get more bleeding-edge than that... breakages are expected, and fixes should NOT be expected in a timely manner, 5.9999 has a very low priority.
Fixed in git https://gitweb.gentoo.org/proj/qt.git/commit/?id=942576847685e455639de9c2f6f431d42ee83445
*** Bug 558302 has been marked as a duplicate of this bug. ***
