public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug build/31958] New: aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71
@ 2024-07-05 23:36 skpgkp2 at gmail dot com
2024-07-06 0:54 ` [Bug build/31958] " skpgkp2 at gmail dot com
2024-07-06 0:55 ` sam at gentoo dot org
0 siblings, 2 replies; 3+ messages in thread
From: skpgkp2 at gmail dot com @ 2024-07-05 23:36 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31958
Bug ID: 31958
Summary: aclocal.m4:6: error: Exactly version 2.72 of Autoconf
is required but you have 2.71
Product: glibc
Version: 2.40
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: skpgkp2 at gmail dot com
CC: carlos at redhat dot com
Target Milestone: ---
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?
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug build/31958] aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71
2024-07-05 23:36 [Bug build/31958] New: aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71 skpgkp2 at gmail dot com
@ 2024-07-06 0:54 ` skpgkp2 at gmail dot com
2024-07-06 0:55 ` sam at gentoo dot org
1 sibling, 0 replies; 3+ messages in thread
From: skpgkp2 at gmail dot com @ 2024-07-06 0:54 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31958
--- Comment #1 from Sunil Pandey <skpgkp2 at gmail dot com> ---
Removed this patch from my local workspace and autoconf works fine. Just
wondering if there is any better method to deal with this situation.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug build/31958] aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71
2024-07-05 23:36 [Bug build/31958] New: aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71 skpgkp2 at gmail dot com
2024-07-06 0:54 ` [Bug build/31958] " skpgkp2 at gmail dot com
@ 2024-07-06 0:55 ` sam at gentoo dot org
1 sibling, 0 replies; 3+ messages in thread
From: sam at gentoo dot org @ 2024-07-06 0:55 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31958
Sam James <sam at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sam at gentoo dot org
--- Comment #2 from Sam James <sam at gentoo dot org> ---
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-07-06 0:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-07-05 23:36 [Bug build/31958] New: aclocal.m4:6: error: Exactly version 2.72 of Autoconf is required but you have 2.71 skpgkp2 at gmail dot com
2024-07-06 0:54 ` [Bug build/31958] " skpgkp2 at gmail dot com
2024-07-06 0:55 ` sam at gentoo dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).