From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: newlib: require autoconf-2.69
Date: Wed, 5 Jan 2022 20:46:21 -0500 [thread overview]
Message-ID: <YdZJ7SfCq+T4BEos@vapier> (raw)
In-Reply-To: <YdWKviY2XmGiqitS@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
On 05 Jan 2022 13:10, Corinna Vinschen wrote:
> On Dec 30 13:39, Mike Frysinger wrote:
> > The top-level newlib dir is already using autoconf-2.69, and all the
> > subdirs are using autoconf-2.68. Update them all to use 2.69 as a
> > prereq and then regenerate them accordingly.
> >
> > The README file already says to use autoconf-2.69.
>
> Yeah, but...
>
> The AC_PREREQ only checks for the minimum required autoconf version for
> *this* specific autoconf file. AC_PREREQ([2.52]) doesn't mean we have to
> use 2.52, but any later version will suffice. All current autoconf
> files are compatible with 2.69. Neither binutils-gdb, nor gcc changed
> their files to require 2.69. So it's note quite clear to me what this
> patch accomplishes.
that's incorrect. gcc & binutils-gdb have config/override.m4 which requires
autoconf-2.69 exactly is used. no older versions, no newer versions, only
2.69 is permitted.
$ cd bfd/
$ autoconf-2.68
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf. It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autoreconf'.
configure.ac:21: error: Please use exactly Autoconf 2.69 instead of 2.68.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:21: the top level
autom4te-2.68: /usr/bin/m4 failed with exit status: 1
$ cd .../gcc/gcc
$ autoconf-2.68
configure.ac:26: error: Please use exactly Autoconf 2.69 instead of 2.68.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:26: the top level
autom4te-2.68: /usr/bin/m4 failed with exit status: 1
do you want me to update newlib/ & libgloss/ to leverage this macro ?
> Autoconf 2.71 is the next version introducing backward incompatibilities.
> Wouldn't it make more sense to fix up the incompatibilities (if any)
> and update the affected files to 2.71 to be more future-proof?
since newlib keeps its top-level files & config/ files in sync with the
binutils-gdb & gcc repos, i don't think moving to a version diff from them
is a good idea. unless you want to completely throw away all of the top
level files and have newlib/libgloss go their own completely independent
route.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-06 1:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 18:39 Mike Frysinger
2022-01-05 12:10 ` Corinna Vinschen
2022-01-05 13:04 ` R. Diez
2022-01-06 1:46 ` Mike Frysinger [this message]
2022-01-06 6:10 ` Mike Frysinger
2022-01-07 9:58 ` Corinna Vinschen
2022-01-07 19:09 ` Mike Frysinger
2022-01-10 9:02 ` Corinna Vinschen
2022-01-11 0:58 ` Mike Frysinger
2022-01-11 10:23 ` Corinna Vinschen
2022-01-12 0:52 ` Mike Frysinger
2022-01-12 10:19 ` Corinna Vinschen
2022-01-12 17:24 ` Mike Frysinger
2022-01-07 9:56 ` Corinna Vinschen
2022-01-07 19:10 ` Mike Frysinger
2022-01-10 9:07 ` Corinna Vinschen
2022-01-12 18:24 ` require autoconf-2.69 exactly Mike Frysinger
2022-01-12 20:01 ` R. Diez
2022-01-12 21:37 ` Mike Frysinger
2022-01-14 10:12 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YdZJ7SfCq+T4BEos@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).