RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
compat-gcc-34 fails because this compiler doesn't seem to know about z9/z10 optimizations, we probably just need to remove those from CFLAGS:
  https://brewweb.devel.redhat.com/getfile?taskID=1943907&name=build.log


for details, talk with Karsten Hopp on #fedora-s390x
This is blocking the RHEL6 Alpha 2

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.