Bug 31958 - aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71
Summary: aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you hav...
Status: UNCONFIRMED
Alias: None
Product: glibc
Classification: Unclassified
Component: build (show other bugs)
Version: 2.40
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-05 23:36 UTC by Sunil Pandey
Modified: 2024-07-06 00:55 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sunil Pandey 2024-07-05 23:36:03 UTC 
This issue appear on Fedora 40, which has autoconf version 2.71 but glibc master moved to 2.72. Following are error message.

$ autoconf configure.ac
aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71 
aclocal.m4:6: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 63

Introduced by following patch.

commit 98ffc1bfeb04fb04b7f18f1cbfccf1e43d6a867f
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Tue Jun 11 23:34:54 2024 +0200

    Convert to autoconf 2.72 (vanilla release, no distribution patches)

Any workaround?
Comment 1 Sunil Pandey 2024-07-06 00:54:09 UTC 
Removed this patch from my local workspace and autoconf works fine. Just wondering if there is any better method to deal with this situation.
Comment 2 Sam James 2024-07-06 00:55:48 UTC 
This would've been a proven if autoconf in Fedora was upgraded too, it just happened on "this side" instead.

I'd really just say either ask them to package individual autoconf versions (we do it in Gentoo, you can make their files not conflict easily) or just build autoconf manually in a custom prefix like /opt/gnu or whatever.