From: Tom Tromey <tom@tromey.com>
To: Christophe Lyon via Gdb <gdb@sourceware.org>
Cc: Christophe Lyon <christophe.lyon@linaro.org>
Subject: Re: [PATCH] contrib: Add autoregen.py
Date: Fri, 19 Apr 2024 10:23:47 -0600 [thread overview]
Message-ID: <87cyqlxqwc.fsf@tromey.com> (raw)
In-Reply-To: <20240419090903.2080043-1-christophe.lyon@linaro.org> (Christophe Lyon via Gdb's message of "Fri, 19 Apr 2024 09:09:03 +0000")
>>>>> Christophe Lyon via Gdb <gdb@sourceware.org> writes:
> This script is a copy of the current script used by Sourceware's
> autoregen buildbots.
> It is intended as a helper to regenerate files managed by autotools
> (autoconf, automake, aclocal, ....), as well as the toplevel
> Makefile.in which is created by autogen.
> Other files can be updated when using maintainer-mode, but this is not
> covered by this script.
Thanks for working on this.
> +# these directories are known to be re-generatable with a simple autoreconf
> +# without special -I flags
Can other directories be updated to this same standard? If not, why
not? I'm somewhat uncomfortable with the number of special cases in
this script.
I was hoping it would be more like:
top level -> autogen + autoconf
anywhere else with configure.{ac,in} -> autoreconf
Tom
next prev parent reply other threads:[~2024-04-19 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:09 Christophe Lyon
2024-04-19 16:23 ` Tom Tromey [this message]
2024-04-19 17:51 ` Simon Marchi
2024-04-30 12:45 ` Christophe Lyon
2024-04-30 17:17 ` Tom Tromey
2024-04-30 18:00 ` Simon Marchi
2024-04-30 22:12 ` Tom Tromey
2024-04-19 22:59 ` Sam James
2024-04-30 12:50 ` Christophe Lyon
2024-04-30 17:59 ` Simon Marchi
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=87cyqlxqwc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=christophe.lyon@linaro.org \
--cc=gdb@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).