From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: binutils@sourceware.org, GCC Mailing List <gcc@gcc.gnu.org>,
gdb-patches@sourceware.org
Subject: Re: Help needed with maintainer-mode
Date: Thu, 29 Feb 2024 12:00:39 +0100 [thread overview]
Message-ID: <20240229110039.GB18580@gnu.wildebeest.org> (raw)
In-Reply-To: <CAPS5khZr3QCN+Ztug-RE4xge+=YGc+hwHWZ8XAhKiQd4X5_O6g@mail.gmail.com>
Hi Christophe,
On Thu, Feb 29, 2024 at 11:22:33AM +0100, Christophe Lyon via Gcc wrote:
> I've noticed that sourceware's buildbot has a small script
> "autoregen.py" which does not use the project's build system, but
> rather calls aclocal/autoheader/automake/autoconf in an ad-hoc way.
> Should we replicate that?
That python script works across gcc/binutils/gdb:
https://sourceware.org/cgit/builder/tree/builder/containers/autoregen.py
It is installed into a container file that has the exact autoconf and
automake version needed to regenerate the autotool files:
https://sourceware.org/cgit/builder/tree/builder/containers/Containerfile-autotools
And it was indeed done this way because that way the files are
regenerated in a reproducible way. Which wasn't the case when using --enable-maintainer-mode (and autoreconfig also doesn't work).
It is run on all commits and warns if it detects a change in the
(checked in) generated files.
https://builder.sourceware.org/buildbot/#/builders/gcc-autoregen
https://builder.sourceware.org/buildbot/#/builders/binutils-gdb-autoregen
Cheers,
Mark
next prev parent reply other threads:[~2024-02-29 11:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 10:22 Christophe Lyon
2024-02-29 10:41 ` Richard Earnshaw (lists)
2024-02-29 17:36 ` Christophe Lyon
2024-02-29 11:00 ` Mark Wielaard [this message]
2024-02-29 17:39 ` Christophe Lyon
2024-03-01 13:08 ` Mark Wielaard
2024-03-01 13:21 ` Christophe Lyon
2024-03-01 16:32 ` Christophe Lyon
2024-03-03 21:15 ` Mark Wielaard
2024-03-04 0:30 ` Sam James
2024-03-04 9:36 ` Thomas Schwinge
2024-03-04 10:42 ` Christophe Lyon
2024-03-04 11:25 ` Jonathan Wakely
2024-03-04 14:46 ` Christophe Lyon
2024-03-04 15:36 ` Richard Earnshaw (lists)
2024-03-04 15:40 ` Richard Earnshaw
2024-03-04 16:42 ` Christophe Lyon
2024-03-04 17:38 ` Richard Earnshaw (lists)
2024-03-04 19:27 ` Vladimir Mezentsev
2024-03-04 20:04 ` Jonathan Wakely
2024-03-05 14:26 ` Richard Earnshaw (lists)
2024-03-05 15:39 ` Richard Earnshaw
2024-03-06 15:04 ` Andrew Carlotti
2024-03-06 17:22 ` Richard Earnshaw (lists)
2024-02-29 19:49 ` Thiago Jung Bauermann
2024-03-01 10:09 ` Christophe Lyon
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=20240229110039.GB18580@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@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).