Bug 519507
Summary: | compat-gcc-34 does not build on S390 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Denise Dumas <ddumas> |
Component: | compat-gcc-34 | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michal Nowak <mnowak> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | ebachalo, karsten, mnowak, notting, ohudlick, syeghiay |
Target Milestone: | alpha | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | compat-gcc-34-3.4.6-18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-02 18:55:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Denise Dumas
2009-08-26 21:16:24 UTC
Easily fixable by trimming the OPT_FLAGS similar to what we already do for the other archs. The only question is if we should use -march=z900 or -march=z990. I've already successfully tested a build with these modifications at http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1948114 We should use the same options as were used in RHEL4 (where gcc 3.4 was the primary compiler), as that's what was tested most. I believe we didn't pass any special -march= nor -mtune= for s390/s390x at that time, so we should just strip it from OPT_FLAGS on these arches. fixed in compat-gcc-34-3.4.6-18 fixed in compat-gcc-34-3.4.6-18 Fixed in 'compat-gcc-34-3.4.6-18', included in compose 'RHEL6.0-20091027.3'. Moving to ON_QA. Verified that compat-gcc-34-3.4.6-18 build for s390x another proof that compat-gcc-34-3.4.6-18 can be build is here: http://download.devel.redhat.com/brewroot/packages/compat-gcc-34/3.4.6/18/. Also had a look at changes 13 v. 18 in CVS and the changes are those proposed in this BZ. Red Hat Enterprise Linux Beta 2 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |