From: Andreas Schwab <schwab@suse.de>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <3246251196ryan@gmail.com>, <gcc-patches@gcc.gnu.org>,
Iain Sandoe <iain@sandoe.co.uk>, <gcc@gcc.gnu.org>,
Paolo Bonzini <bonzini@gnu.org>,
Nathanael Nerode <neroden@gcc.gnu.org>,
Alexandre Oliva <aoliva@gcc.gnu.org>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
"Joseph Myers" <joseph@codesourcery.com>
Subject: Re: Enable top-level recursive 'autoreconf'
Date: Thu, 19 Oct 2023 11:57:33 +0200 [thread overview]
Message-ID: <mvmo7gv9boy.fsf@suse.de> (raw)
In-Reply-To: <87v8b37ye7.fsf@euler.schwinge.homeip.net> (Thomas Schwinge's message of "Thu, 19 Oct 2023 11:30:08 +0200")
On Okt 19 2023, Thomas Schwinge wrote:
> Hi!
>
> On 2023-10-18T15:42:18+0100, R jd <3246251196ryan@gmail.com> wrote:
>> I guess I can ask, why there is not a recursive approach for configuring
>> GCC. e.g. AC_SUBDIRS in the top level?
>
> ('AC_CONFIG_SUBDIRS' you mean.) You know, often it just takes someone to
> ask the right questions... ;-)
>
> What do people think about the attached
> "Enable top-level recursive 'autoreconf'"? Only lightly tested, so far.
The top-level files are shared with binutils-gdb, which has a different
set of subdirs.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-10-19 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPB2dxkMVi=ijhoOo7YVugVPAo3WeOvEpk_FvQMxU7F0BcP2Gw@mail.gmail.com>
[not found] ` <4BD76988-F7CE-4AD1-8802-BAE371D1F9F5@sandoe.co.uk>
[not found] ` <875y343xah.fsf@euler.schwinge.homeip.net>
[not found] ` <CAPB2dxmWCU9vzu-=BqB1ZfYBq8GoQRNDBf4gYy_GvnB40tPA=Q@mail.gmail.com>
2023-10-19 9:30 ` Enable top-level recursive 'autoreconf' (was: Hints on reconfiguring GCC) Thomas Schwinge
2023-10-19 9:57 ` Andreas Schwab [this message]
2023-10-19 10:42 ` Enable top-level recursive 'autoreconf' Thomas Schwinge
2023-10-19 23:13 ` Eric Gallager
2023-10-30 1:31 ` Hans-Peter Nilsson
2023-10-20 4:07 ` Alexandre Oliva
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=mvmo7gv9boy.fsf@suse.de \
--to=schwab@suse.de \
--cc=3246251196ryan@gmail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=joseph@codesourcery.com \
--cc=neroden@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/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).