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.
This issue will start impacting m4 in Red Hat Enterprise Linux 9 once we switch to glibc 2.34.
[[[EDIT No longer applicable, a regular build with suffice EDIT]]]
You can test a fix before glibc 2.34 is merged using this command:
koji -p stream build --scratch c9s-build-side-102-stack-gate git+https://gitlab.com/redhat/centos-stream/rpms/m4#origin/c9s
+++ This bug was initially created as a clone of Bug #1943033 +++
Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
--- Additional comment from Vitezslav Crhonek on 2021-03-29 13:08:41 CEST ---
This doesn't look like fail because autoconf, but because of recent change in glibc. It's already discussed at m4 upstream
mailing list and also at [1].
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=20305
--- Additional comment from Ondrej Dubaj on 2021-04-12 09:13:10 CEST ---
Gentle ping.
--- Additional comment from Ernestas on 2021-04-13 11:25:58 CEST ---
There’s no obvious interest upstream, so maybe this should be reassigned to glibc or another bug should be created there for extra eyes.
--- Additional comment from Florian Weimer on 2021-04-14 09:53:51 CEST ---
There is currently no plan to revert the glibc change. m4 has to be fixed. Thanks.
--- Additional comment from Vitezslav Crhonek on 2021-05-10 13:20:34 CEST ---
(In reply to Ernestas from comment #3)
> There’s no obvious interest upstream, so maybe this should be reassigned to
> glibc or another bug should be created there for extra eyes.
Upstream has released 1.4.18b that fixes this issue (inherits the fix from gnulib).
I've created COPR repo with that release:
https://copr.fedorainfracloud.org/coprs/vcrhonek/m4-test/
Stable 1.4.19 is going to be released later this month.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: m4), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2605