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.
Description of problem: The AC_OPENMP macro throws an error and exits if the language is set to Fortran or Fortran 77.
Version-Release number of selected component (if applicable): 2.63-5.1.el6
How reproducible: 100%
Steps to Reproduce:
1. Create a simple configure.ac with the following contents:
[prescott@gator1 bar]$ cat configure.ac
AC_INIT
AC_LANG(Fortran)
AC_OPENMP
2. Run autoconf.
Actual results:
[prescott@gator1 bar]$ autoconf
configure.ac:3: error: AC_LANG_FUNC_LINK_TRY: unknown language: Fortran
../../lib/autoconf/lang.m4:228: AC_LANG_FUNC_LINK_TRY is expanded from...
../../lib/autoconf/c.m4:1879: _AC_LANG_OPENMP is expanded from...
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2518: AC_LINK_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
../../lib/autoconf/general.m4:1974: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1994: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/c.m4:1917: AC_OPENMP is expanded from...
configure.ac:3: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
Expected results:
Exit status of 0 with correctly generated configure script.
Additional info:
For AC_LANG(Fortran 77), the result is:
configure.ac:3: error: AC_LANG_FUNC_LINK_TRY: unknown language: Fortran 77
../../lib/autoconf/lang.m4:228: AC_LANG_FUNC_LINK_TRY is expanded from...
../../lib/autoconf/c.m4:1879: _AC_LANG_OPENMP is expanded from...
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2518: AC_LINK_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
../../lib/autoconf/general.m4:1974: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1994: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/c.m4:1917: AC_OPENMP is expanded from...
configure.ac:3: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
Created attachment 819285[details]
AC_OPENMP patch
I made a patch based upon the thread in comment #1 (added Fortran to it, but skipped the test patches), added it to my spec file and rebuilt the autoconf rpm. It resolved the issues I observed.
Sorry for late posting and thanks for pointing the upstream resolution.
Craig, bugzilla for RHEL product is just an bug tracking tool and engineering
is not able to guarantee the timeliness (priority of this particular issue).
I'll keep this bug open though to make a chance to raise proper
prioritization.
If this issue is critical or in any way time sensitive, please raise a ticket
through your regular Red Hat support channels to make certain it receives the
proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please
visit: https://www.redhat.com/support/process/production/#howto