From: Christophe Lyon <christophe.lyon@linaro.org>
To: Simon Marchi <simark@simark.ca>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH] autoregen.py: Use autoreconf by default
Date: Tue, 30 Apr 2024 10:50:51 +0200 [thread overview]
Message-ID: <CAPS5khaOqzWoCs9sXjBTicnOu+SAo9TUg3HHRuQwLSHYw=QxXw@mail.gmail.com> (raw)
In-Reply-To: <95a67e33-662e-4d74-9dac-3e168618c827@simark.ca>
On Tue, 30 Apr 2024 at 04:26, Simon Marchi <simark@simark.ca> wrote:
>
>
>
> On 2024-04-29 08:27, Christophe Lyon wrote:
> > On Mon, 29 Apr 2024 at 05:28, Simon Marchi <simark@simark.ca> wrote:
> >>
> >>
> >>
> >> On 2024-04-28 17:23, Christophe Lyon wrote:
> >>> Since the list of directories compatible with autoreconf is large,
> >>> make it the default, and introduce a list of directories to
> >>> reconfigure 'manually'.
> >>
> >> The patch looks fine to me. I think we can clean up some things that
> >> are no longer needed and make the code a bit nicer. I can send a patch
> >> series for this once this one is merged (I don't want to create
> >> unnecessary conflicts).
> >>
> >
> > Thanks for your comments.
> >
> > Mark, if you are happy with the changes, can you apply this patch?
> >
> > Thanks,
> >
> > Christophe
> >
> >> Simon
>
> FYI, I sent these two patches to gcc-patches to try to get rid of the
> quirks entirely:
>
> https://inbox.sourceware.org/gcc-patches/20240430020040.92188-1-simon.marchi@polymtl.ca/T/#u
> https://inbox.sourceware.org/gcc-patches/20240430022420.114397-1-simon.marchi@polymtl.ca/T/#u
>
> If these (or equivalent) get merged, then we'll be able to do everything
> with autoreconf, it will simplify things a lot.
>
Great, thanks!
Christophe
> Simon
prev parent reply other threads:[~2024-04-30 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 21:23 Christophe Lyon
2024-04-29 3:28 ` Simon Marchi
2024-04-29 12:27 ` Christophe Lyon
2024-04-29 16:44 ` Mark Wielaard
2024-04-30 2:26 ` Simon Marchi
2024-04-30 8:50 ` Christophe Lyon [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='CAPS5khaOqzWoCs9sXjBTicnOu+SAo9TUg3HHRuQwLSHYw=QxXw@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=buildbot@sourceware.org \
--cc=simark@simark.ca \
/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).