Bug 822710
Summary: | Can't build 32bit Qt release application on 64bit | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dominik.Riebeling |
Component: | qt | Assignee: | Than Ngo <than> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | itamar, jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-18 00:42:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dominik.Riebeling
2012-05-17 21:04:48 UTC
Indeed, I don't recall all the history/rationale behind modifying the mkspecs/common/g*base.conf files right now, but, since it causes bad side-effects... I'll see if we can avoid doing that. Looks like that approach works, I'll whip up a fix to commit. In the meantime... This still won't use the fedora default compiler flags for non-native builds this way however (that's a separate problem which may not be reasonably solvable, past attemps have failed) To achieve that on a 64bit fedora system now, you'd need to run /usr/lib/qt4/bin/qmake instead of the native 64bit one (via either /usr/bin/qmake-qt4 or /usr/lib64/qt4/bin/qmake) http://pkgs.fedoraproject.org/gitweb/?p=qt.git;a=commit;h=e0673557d0252b5de1146d15ce9fa41e1714c6f7 fixed in rawhide, will be rolled into the next qt update we do for f16 (You can use the workarounds I suggested in the meantime, I hope) The rationale behind modifying g*base.conf was probably to ensure that even non-RPM builds default to our default flags. I'm nervous about changing this, it might also affect some package builds. Not all specfiles set CFLAGS explicitly. I tested and made sure the flags still get set via mkspecs/default/qmake.conf As a matter of fact, I'd noticed the RPM_OPT_FLAGS were appearing twice for some time now, and had been thinking of looking into why that was happening. turned out to be this. |