From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss/newlib: rename configure.in to configure.ac
Date: Tue, 14 Sep 2021 10:38:53 +0200 [thread overview]
Message-ID: <YUBfnejuodZQL4Ya@calimero.vinschen.de> (raw)
In-Reply-To: <YUARGuL4RzvSjEay@vapier>
On Sep 13 23:03, Mike Frysinger wrote:
> On 14 Sep 2021 00:54, Hans-Bernhard Bröker wrote:
> > Am 13.09.2021 um 16:13 schrieb Mike Frysinger:
> > > 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.
> >
> > The name of configure.{in|ac} is supposed to show up in just about every
> > Makefile.in. The maintainer rules to update configure rely on that.
> > Automake-generated Makefile.in pick up this change automatically.
>
> thanks for pointing this out. i sent a patch for it.
>
> > libgloss doesn't use automake, so there you would have to do all this by
> > hand. Or keep on not doing it at all: at the moment there are no such
> > maintainer-specific rules in the libgloss Makefile.in except in
> > libgloss/wince, which does use automake.
>
> the wince dir is running ancient automake-1.4 still. the rest of newlib
> is at least up on automake-1.11, but even that should get moved to 1.15
> like the rest of the projects. but that's prob another yak shave i'm not
> in the mood to tackle.
>
> > > i agree that we should add
> > > a macro to enforce a specific autoconf version and regen everything with
> > > that :).
> >
> > No need to add one ;-). That's precisely what config/override.m4
> > already does.
> >
> > The entire newlib tree relies quite heavily on features that have been
> > dropped from autoconf a _long_ time ago. The version it requires is 2.64
> > from the year 2008. Getting all that resolved takes quite a bit more
> > effort than just renaming files and dropping the explicit restriction.
> > Every single Makefile.am and configure.ac has to be modified to remove
> > things like the cygnus mode option to automake, or the outdated use of
> > INCLUDES instead of AM_CPPFLAGS.
>
> there are large variety of autoconf versions in use in the tree :(.
> $ find newlib/ libgloss/ -name configure -exec sed -n '/Generated by GNU Autoconf/p' {} + | sort | uniq -c
> 1 # Generated by GNU Autoconf 2.59.
> 26 # Generated by GNU Autoconf 2.61.
> 6 # Generated by GNU Autoconf 2.63.
> 2 # Generated by GNU Autoconf 2.64.
> 2 # Generated by GNU Autoconf 2.66.
> 11 # Generated by GNU Autoconf 2.68.
> 1 # Generated by GNU Autoconf 2.68 for libepiphany 0.0.1.
> 1 # Generated by GNU Autoconf 2.68 for libgloss LIBGLOSS_VERSION.
> 1 # Generated by GNU Autoconf 2.68 for libor1k 0.0.1.
> 2 # Generated by GNU Autoconf 2.68 for newlib 2.5.0.
> 112 # Generated by GNU Autoconf 2.68 for newlib 4.1.0.
> 3 # Generated by GNU Autoconf 2.69.
> -mike
The versions Jeff and I use for newlib are
aclocal-1.11.6 -I. -I.. -I ../.. -I ../../..
autoconf-2.68
automake-1.11.6 --cygnus --no-force
The problem is to revamp the newlib tree to do the right thing without
the dreaded --cygnus option. In the meantime we are using the latest
automake/autoconf tools at least in the Cygwin part of the repo, thanks
to Jon Turney.
Corinna
next prev parent reply other threads:[~2021-09-14 8:39 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
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 [this message]
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=YUBfnejuodZQL4Ya@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).