Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Previously a regression in the gfortran compiler was causing the "-M" option to not be recognized. In these updated packages the "-M" option is now recognized and functions as expected.
DescriptionSiddhesh Poyarekar
2011-02-04 12:31:51 UTC
Created attachment 476992[details]
Backport from r162990 upstream
Description of problem:
gfortran no longer recognizes the -M* options in gcc-4.4. This is a regression in gcc-4.4 caused when gfortran moved from cc1 to libcpp for its external preprocessor. The feature works correctly in RHEL-5. The bug has been documented and fixed upstream:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43954
How Reproducible:
Always
Steps to Reproduce:
root@gncc mtest # cat mtest.F
#include "mtest.h"
x(1) = 2
print 10, x(1)
10 format(' Hello World, x(1) =', i5)
end
root@gncc mtest # cat mtest.h
integer x(10)
root@gncc mtest # gcc -M mtest.F
Actual Result:
root@gncc mtest # gcc -M mtest.F
f951: warning: command line option "-M" is valid for C/C++/Java/ObjC/ObjC++ but not for Fortran
Expected Result:
root@gncc mtest # gcc -M mtest.F
mtest.o: mtest.F mtest.h
This has been committed to upstream 4.4 branch on
Date: Sun Aug 8 01:59:15 2010
therefore it is in RHEL6.1 gcc-4.4.5-5.el6, which is currently based on
20110117 snapshot.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously a regression in the gfortran compiler was causing the "-M*" options to not be recognized. In these updated packages the "-M*" options are now recognized and function as expected.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Previously a regression in the gfortran compiler was causing the "-M*" options to not be recognized. In these updated packages the "-M*" options are now recognized and function as expected.+Previously a regression in the gfortran compiler was causing the "-M" option to not be recognized. In these updated packages the "-M" option is now recognized and functions as expected.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0663.html