From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: newlib: require autoconf-2.69
Date: Mon, 10 Jan 2022 19:58:47 -0500 [thread overview]
Message-ID: <YdzWR9EFxM6Rvsr5@vapier> (raw)
In-Reply-To: <Ydv2H7ih/92Ap1kj@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
On 10 Jan 2022 10:02, Corinna Vinschen wrote:
> On Jan 7 14:09, Mike Frysinger wrote:
> > On 07 Jan 2022 10:58, Corinna Vinschen wrote:
> > > On Jan 6 01:10, Mike Frysinger wrote:
> > > > On 05 Jan 2022 20:46, Mike Frysinger wrote:
> > > > > do you want me to update newlib/ & libgloss/ to leverage this macro ?
> > > >
> > > > looks like it's just as easy as passing -I to the top-level config dir when
> > > > running aclocal. since override.m4 overrides AC_INIT, it forces the version
> > > > lock logic. example diff for newlib/ is below.
> > > >
> > > > lmk what you prefer here.
> > >
> > > No worries. I guess it's really better to stick to the same autoconf
> > > requirements as gcc/binutils-gdb.
> >
> > is that an approval to push the override.m4 approach ? :)
>
> That was an approval to push your original patch as is, but I'd like
> an approach to tweak and use override.m4 better, me thinks. Do you
> want to submit a patch for this?
i've posted two patches at this point. the first one in this thread which only
changed the AC_PREREQ lines, and a second one to leverage override.m4:
https://sourceware.org/pipermail/newlib/2022/018829.html
granted, it wasn't every single subdir, but that example patch is what i used
everywhere and the resulting diff was basically copied & pasted.
or do you want a patch that updates AC_PREREQ & uses override.m4 ?
or do you want a patch that deletes AC_PREREQ & uses override.m4 ?
with the override.m4 logic, AC_PREREQ is completely redundant.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-11 0:58 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
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 [this message]
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=YdzWR9EFxM6Rvsr5@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).