Summary: | x11-libs/qt-* fail to cross-compile, probably not respecting *FLAGS at compile time | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Sachau <tommy> |
Component: | New packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | autobuilds | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Thomas Sachau
2011-12-18 13:23:48 UTC
Probably an eclass change broke the build... Could you please search your emerge.log for the last successful merge of qt-{core,gui}-4.7.4 and tell me when that happened? Fri Sep 9 18:48:51 2011 >>> x11-libs/qt-core-4.7.4 Sun Sep 18 16:47:27 2011 >>> x11-libs/qt-gui-4.7.4 As already mentioned in some other places, beside changes in ebuilds or eclasses, profile changes might also be related, in this case this one: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/arch/amd64/make.defaults?r1=1.9&r2=1.10 If ebuilds or eclasses pull in the default flags for the current host (in this case -m64) independent from the target, this could overwrite the already added -m32 to cross-compile for x86. I just realized the build fails at configure time, so this is probably a duplicate of bug #336618. Bug #336618 has been fixed, could you try to reproduce this issue again please? thanks, both qt-core and qt-gui tested and compiled fine *** This bug has been marked as a duplicate of bug 336618 *** |