From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: require autoconf-2.69 exactly
Date: Fri, 14 Jan 2022 11:12:10 +0100 [thread overview]
Message-ID: <YeFMeuHgz4jztRs/@calimero.vinschen.de> (raw)
In-Reply-To: <Yd8c+05scrOedGdq@vapier>
On Jan 12 13:24, Mike Frysinger wrote:
> 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.
>
> The README file already says to use autoconf-2.69.
>
> To accomplish this, it's just as simple as adding -I flags to the
> top-level config/ dir when running aclocal. This is because the
> override.m4 file overrides AC_INIT to first require the specific
> autoconf version before calling the real AC_INIT.
> ---
> attaching compressed as it's too big for the list
LGTM, please push.
Thanks,
Corinna
prev parent reply other threads:[~2022-01-14 10:12 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
2022-01-12 21:37 ` Mike Frysinger
2022-01-14 10:12 ` Corinna Vinschen [this message]
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=YeFMeuHgz4jztRs/@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).