From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: newlib@sourceware.org
Subject: Re: require autoconf-2.69 exactly
Date: Wed, 12 Jan 2022 21:01:01 +0100 [thread overview]
Message-ID: <81f7aca6-e34a-cfec-1181-001e0e00ea8a@yahoo.de> (raw)
In-Reply-To: <Yd8c+05scrOedGdq@vapier>
> The newlib & libgloss dirs are already generated using autoconf-2.69.
> To avoid merging new code and/or accidental regeneration using diff
> versions, leverage config/override.m4 to pin to 2.69 exactly. This
> matches what gcc/binutils/gdb are already doing.
Pinning to exactly version 2.69 is a strange thing to do.
I have been using Autoconf 2.69 for years in my embedded firmware project, and when 2.70 and 2.71 came out not long ago, I upgraded without any
trouble. They also bring a raft of general improvements.
Is there a reason why Newlib must be exactly be in sync with whatever GCC etc. do?
The regeneration problems you have every now and then are a consequence of checking in the files that the Autotools generate. You are not supposed to
do that. Anybody directly using a source code repository should be running some bootstrap script, perhaps with a common name like autogen.sh, in order
to generate the Autotools files first.
The release tarballs you generate here should include the generated Autotools files:
ftp://sourceware.org/pub/newlib/
That is, assuming you could actually access an FTP server with a modern browser.
I am sure you know that this is standard practice with the Autotools. I can imagine some delay implementing it until the whole Autotools mess in
Newlib has been cleaned up (which is a great thing to do, by the way). But pinning to an exact Autoconf version seems like a step in the wrong direction.
Regards,
rdiez
next prev parent reply other threads:[~2022-01-12 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 18:39 newlib: require autoconf-2.69 Mike Frysinger
2022-01-05 12:10 ` Corinna Vinschen
2022-01-05 13:04 ` R. Diez
2022-01-06 1:46 ` Mike Frysinger
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 [this message]
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=81f7aca6-e34a-cfec-1181-001e0e00ea8a@yahoo.de \
--to=rdiezmail-newlib@yahoo.de \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).