/usr/lib64/qt5/bin/qmake -o qtdetail.mk qtdetail.pro Info: creating stash file /var/tmp/portage/dev-python/PyQt5-5.8.2/work/PyQt5_gpl-5.8.2-python2_7/.qmake.stash Project ERROR: Unknown module(s) in QT: gui * ERROR: dev-python/PyQt5-5.8.2::gentoo failed (configure phase): * (no error message) * ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-systemd-abi32+64_20170409-195332) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2:
Created attachment 470034 [details] emerge-info.txt
Created attachment 470036 [details] dev-python:PyQt5-5.8.2:20170413-232507.log
Created attachment 470038 [details] emerge-history.txt
Created attachment 470040 [details] environment
Created attachment 470042 [details] etc.portage.tbz2
Created attachment 470044 [details] temp.tbz2
I consider this an upstream bug. The qtdetail program used by configure.py requires QtGui, even if we're building bindings only for QtCore.
In 5.9 and later, the config detection program was split in multiple pieces, and the program for QtCore (cfgtest_QtCore) is explicitly built with "QT -= gui". So, this issue should be fixed.
