This is an auto-filled bug because dev-qt/qtxml calls directly g++. Attached build log and emerge --info
Created attachment 633174 [details] build.log build log and emerge --info
this is confirmed for all dev-qt/qt* packages not just qtxml
I guess it is an eclass bug. in qt5-build_src_prepare() there is: # Respect CC, CXX, *FLAGS, MAKEOPTS and EXTRA_EMAKE when bootstrapping qmake sed -i -e "/outpath\/qmake\".*\"\$MAKE\")/ s|)| \ ${MAKEOPTS} ${EXTRA_EMAKE} 'CC=$(tc-getCC)' 'CXX=$(tc-getCXX)' \ 'QMAKE_CFLAGS=${CFLAGS}' 'QMAKE_CXXFLAGS=${CXXFLAGS}' 'QMAKE_LFLAGS=${LDFLAGS}'&|" \ -e 's/\(setBootstrapVariable\s\+\|EXTRA_C\(XX\)\?FLAGS=.*\)QMAKE_C\(XX\)\?FLAGS_\(DEBUG\|RELEASE\).*/:/' \ configure || die "sed failed (respect env for qmake build)" But in the practice it does not work at least for CXX/g++
*** Bug 725956 has been marked as a duplicate of this bug. ***
Created attachment 643294 [details, diff] qtbase-by-qt5-build.eclass.diff The above sed at least is still doing something in configure file - attaching diff that is the result of qt5-build_src_prepare on my system. However, this one is a no-op: > # Respect CXX in bsymbolic_functions, fvisibility, precomp, and a few other tests > sed -i -e "/^QMAKE_CONF_COMPILER=/ s:=.*:=\"$(tc-getCXX)\":" \ > configure || die "sed failed (QMAKE_CONF_COMPILER)" QMAKE_CONF_COMPILER var is gone since this commit: https://github.com/qt/qtbase/commit/90eee08b3e672573e3ad93470d844e1d498651dd
(In reply to Agostino Sarubbo from comment #2) > this is confirmed for all dev-qt/qt* packages not just qtxml It affects far more than just that too, and is currently the leading cause of tc-direct based failures on my rig. Samples include: * app-editors/tea * app-mobilephone/qtadb * media-video/baka-mplayer * app-text/qpdfview
*** Bug 734860 has been marked as a duplicate of this bug. ***