From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss/newlib: rename configure.in to configure.ac
Date: Mon, 13 Sep 2021 10:13:52 -0400 [thread overview]
Message-ID: <YT9coInuYGMW+eTy@vapier> (raw)
In-Reply-To: <YT8kGvNQCfpoiENw@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On 13 Sep 2021 12:12, Corinna Vinschen wrote:
> On Sep 9 17:06, Mike Frysinger wrote:
> > The .in name has been deprecated for a long time in favor of .ac.
>
> ACK. Are you going to regen afterwards?
that should be a nop as the filename input shouldn't affect the output.
i confirmed on one or two dirs.
if you mean was i planning on regenerating with the latest version of
autoconf everywhere, then no, i'm not intending on doing that. i first
tried to use autoconf-2.69 (since that's what binutils+gdb require), but
it failed on a bunch of dirs, and i didn't feel like digging through all
the failures to figure out what's going on. i agree that we should add
a macro to enforce a specific autoconf version and regen everything with
that :).
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-13 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 21:06 Mike Frysinger
2021-09-13 10:12 ` Corinna Vinschen
2021-09-13 14:13 ` Mike Frysinger [this message]
2021-09-13 22:54 ` Hans-Bernhard Bröker
2021-09-14 2:58 ` [PATCH] libgloss/newlib: update configure.ac in Makefile.in files Mike Frysinger
2021-11-06 18:18 ` Mike Frysinger
2021-09-14 3:03 ` [PATCH] libgloss/newlib: rename configure.in to configure.ac Mike Frysinger
2021-09-14 8:38 ` Corinna Vinschen
2021-09-15 5:05 ` Mike Frysinger
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=YT9coInuYGMW+eTy@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).