From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/5] start converting libgloss to non-recursive automake
Date: Tue, 8 Feb 2022 10:15:32 +0100 [thread overview]
Message-ID: <YgI0tLWTEk3EotFG@calimero.vinschen.de> (raw)
In-Reply-To: <YgEUej2xhPZK500d@vapier>
On Feb 7 07:45, Mike Frysinger wrote:
> On 07 Feb 2022 12:36, Corinna Vinschen wrote:
> > On Feb 5 00:46, Mike Frysinger wrote:
> > > This converts the top-level to automake, and then cuts a few subdirs over
> > > to non-recursive automake. I didn't cut all the subdirs over to automake,
> > > but should be easy to convert more over.
> > >
> > > Mike Frysinger (5):
> > > libgloss: convert top level to automake
> > > libgloss: merge doc into top-level Makefile
> > > libgloss: merge libgloss into top-level Makefile
> > > libgloss: merge iq2000 into top-level Makefile
> > > libgloss: merge bfin into top-level Makefile
> >
> > $ autoreconf
> > configure.ac:46: warning: macro 'AM_ENABLE_MULTILIB' not found in library
> > configure.ac:31: warning: macro 'AM_ENABLE_MULTILIB' not found in library
> > [...]
> >
> > Problem? A dependency to another not yet applied patch?
>
> this isn't new behavior. although i understand the mismatch in expectations.
>
> if you run `autoreconf` in libgloss/ today, you will see these same warnings.
> it's because the only way to have aclocal search extra dirs for m4 macros is
> either pass the -I flags to autoreconf directly, or have a Makefile.am with
> ACLOCAL_AMFLAGS set in it (which autoreconf extracts and passes to aclocal).
>
> w/out automake, ACLOCAL_AMFLAGS doesn't work, so you have to add all the -I
> flags yourself with absolute paths:
> $ autoreconf -I $PWD -I $PWD/.. -I $PWD/../config
>
> yes, i'm converting the top-level to automake, so the ACLOCAL_AMFLAGS are
> picked up from there, but that's only the top-level. autoreconf will go
> into each subdir and run autoreconf in there, and that's where these are
> coming from. once all the subdirs convert over to automake, then you can
> go back to running plain `autoreconf` and it'll all just work for you.
>
> if you run `autoreconf -v`, it's a little more obvious that it's coming
> from the subdirs as it'll show:
> autoreconf-2.69: configure.ac: adding subdirectory aarch64 to autoreconf
> autoreconf-2.69: Entering directory `aarch64'
> autoreconf-2.69: running: aclocal
> configure.ac:46: warning: macro 'AM_ENABLE_MULTILIB' not found in library
> -mike
Ok, thanks for this and your other reply. GTG.
Corinna
prev parent reply other threads:[~2022-02-08 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 5:46 Mike Frysinger
2022-02-05 5:46 ` [PATCH 1/5] libgloss: convert top level to automake Mike Frysinger
2022-02-05 5:46 ` [PATCH 2/5] libgloss: merge doc into top-level Makefile Mike Frysinger
2022-02-05 5:46 ` [PATCH 3/5] libgloss: merge libgloss " Mike Frysinger
2022-02-07 11:14 ` Mike Frysinger
2022-02-07 11:49 ` Corinna Vinschen
2022-02-05 5:46 ` [PATCH 4/5] libgloss: merge iq2000 " Mike Frysinger
2022-02-05 5:46 ` [PATCH 5/5] libgloss: merge bfin " Mike Frysinger
2022-02-07 11:44 ` Corinna Vinschen
2022-02-07 12:07 ` Corinna Vinschen
2022-02-07 13:11 ` Mike Frysinger
2022-02-07 11:36 ` [PATCH 0/5] start converting libgloss to non-recursive automake Corinna Vinschen
2022-02-07 12:45 ` Mike Frysinger
2022-02-08 9:15 ` 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=YgI0tLWTEk3EotFG@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).