x11-libs/qt-core-4.4.2-r2 fails to compile using distcc across multiple computers with different CHOSTs, because it calls g++ directly rather than the CHOST specific compiler. Reproducible: Always Steps to Reproduce: 1. Set up crossdev and distcc on a machine with a different CHOST than the emerging machine 2. emerge x11-libs/qt-core-4.4.2-r2 using distcc and the helper machine with a different CHOST Actual Results: qt-core fails to build properly. although the build.log just lists the qmake calls and not what qmake is calling, running qmake manually on the source produces output like: Creating qmake. Please wait... g++ -c -o option.o -pipe -DQMAKE_OPENSOURCE_EDITION -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include/QtCore -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include/QtCore -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/src/corelib/global -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/src/script -DQT_NO_PCRE -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_BUILD_QMAKE -DQT_NO_COMPRESS -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT option.cpp g++ -c -o qlibraryinfo.o -pipe -DQMAKE_OPENSOURCE_EDITION -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include/QtCore -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/include/QtCore -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/src/corelib/global -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/src/script -DQT_NO_PCRE -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_BUILD_QMAKE -DQT_NO_COMPRESS -I/var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT /var/tmp/portage/x11-libs/qt-core-4.4.2-r2/work/qt-x11-opensource-src-4.4.2/src/corelib/global/qlibraryinfo.cpp etc... where g++ rather than, for example, x86_64-pc-linux-gnu-g++ is executed. Expected Results: The correct CHOST specific compiler should be executed, and the build should succeed. Sorry if this is the wrong category, I wasn't sure if this should go in dev or KDE or what. Also, I would guess (but have not yet verified) that the other qt builds fail similarly.
Please post your `emerge --info' too.
Created attachment 189909 [details] emerge --info from the emerging machine emerge --info from the emerging machine. Also, FYI, all other qt-foobar builds fail similarly, unless distcc is totally disabled.. even distcc across hosts with the same CHOST seems to fail.....
does this still happen with 4.5.1? i managed to compile 4.5.1 with distcc between sparc and amd64 systems
Indeed 4.5.X packages work fine. I 'll close this bug as WONTFIX cause we wont bother to fix the old packages since qt-4.5.1 will be stable soon
