Created attachment 301565 [details] build.log without test USE="-*" emerge -v =dev-python/pyside-1.1.0 [ 63%] Building CXX object PySide/QtCore/CMakeFiles/QtCore.dir/glue/qeasingcurve_glue.cpp.o Linking CXX shared module ../QtCore.so [ 63%] Built target QtCore make: *** [all] Errore 2 * ERROR: dev-python/pyside-1.1.0 failed (compile phase): * emake failed FEATURES="-test" USE="-*" emerge -v =dev-python/pyside-1.1.0 [ 96%] Building CXX object PySide/QtNetwork/CMakeFiles/QtNetwork.dir/PySide/QtNetwork/qsslsocket_wrapper.cpp.o /var/tmp/portage/dev-python/pyside-1.1.0/work/pyside-1.1.0_build/PySide/QtNetwork/PySide/QtNetwork/qsslsocket_wrapper.cpp: In member function ‘virtual qint64 QSslSocketWrapper::readData(char*, qint64)’: /var/tmp/portage/dev-python/pyside-1.1.0/work/pyside-1.1.0_build/PySide/QtNetwork/PySide/QtNetwork/qsslsocket_wrapper.cpp:494:12: warning: ‘cppResult’ may be used uninitialized in this function Linking CXX shared module ../QtNetwork.so [ 96%] Built target QtNetwork make: *** [all] Errore 2 * ERROR: dev-python/pyside-1.1.0 failed (compile phase): * emake failed
Created attachment 301567 [details] build.log with test
FEATURES="-test" Could you try "USE=-* test" and see what happens?
What I meant is: Could you try FEATURES="-test" USE="-*test" and see what happens?
FEATURES="-test" USE="-* test" emerge -v =dev-python/pyside-1.1.0 exactly the same error as USE="-*" emerge -v =dev-python/pyside-1.1.0 stopped at 63%
As far as I can tell currently setting USE="-X" breaks it. Looks like the build system has a bug with it as it appears to fail to find QtNetwork (part of qt-core) when USE="-X", but finds it with USE="X"
So, who is willing to report that upstream?
(In reply to comment #6) > So, who is willing to report that upstream? This is not an upstream bug.
This is fixed in =dev-python/pyside-1.1.0-r1 which will be unmasked soon. There were two separate issues actually: the first one was a bug in the ebuild, which was trying to building QtTest bindings without respecting the internal dependencies between PySide modules, and this is now fixed; the second issue was that upstream really requires QtGui (and the corresponding PySide module) in order to build and run the test suite, thus I added the appropriate REQUIRED_USE constraint.