From: Christophe Lyon <christophe.lyon@linaro.org>
To: buildbot@sourceware.org
Cc: Christophe Lyon <christophe.lyon@linaro.org>
Subject: [PATCH 0/6] autoregen.py: Improve support for GCC
Date: Fri, 12 Apr 2024 20:05:53 +0000 [thread overview]
Message-ID: <20240412200559.1649050-1-christophe.lyon@linaro.org> (raw)
Hi,
I looked into more details to improve autoregen.py's support for GCC.
I noticed that autoreconf works well in most directories, so this
patch series adds most GCC subdirs to AUTORECONF_DIRS.
Following that, I noticed that quite a few more subdirs from
binutils-gdb can also be regenerated using autoreconf, so add them to
AUTORECONF_DIRS.
In addition, add support for autogen, to regenerate the top-level
Makefile.in.
There are still some peculiarities with some subdirs, so there are
probably some fixes to make in binutils, gdb and gcc. We can update
this script when that is the case.
Also, this script should probably be copied into contrib/ for the
benefit of the projects.
Christophe Lyon (6):
auroregen.py: Check AC_CONFIG_MACRO_DIR instead of
AC_CONFIG_MACRO_DIRS
autoregen.py: Move comment...
autoregen.py: Flush all print commands
autoregen.py: Use autoreconf in most GCC directories
autoregen.py: Add support for autogen
autoregen.py: Add binutils directories to AUTORECONF_DIRS
builder/containers/autoregen.py | 93 +++++++++++++++++++++++++++++++--
1 file changed, 89 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-12 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 20:05 Christophe Lyon [this message]
2024-04-12 20:05 ` [PATCH 1/6] auroregen.py: Check AC_CONFIG_MACRO_DIR instead of AC_CONFIG_MACRO_DIRS Christophe Lyon
2024-04-12 20:05 ` [PATCH 2/6] autoregen.py: Move comment Christophe Lyon
2024-04-12 20:05 ` [PATCH 3/6] autoregen.py: Flush all print commands Christophe Lyon
2024-04-15 2:09 ` Simon Marchi
2024-04-15 11:55 ` Christophe Lyon
2024-04-12 20:05 ` [PATCH 4/6] autoregen.py: Use autoreconf in most GCC directories Christophe Lyon
2024-04-15 3:07 ` Simon Marchi
2024-04-15 12:52 ` Christophe Lyon
2024-04-15 14:48 ` Simon Marchi
2024-04-16 14:47 ` Christophe Lyon
2024-04-16 15:32 ` Simon Marchi
2024-04-16 16:12 ` Christophe Lyon
2024-04-17 14:30 ` Christophe Lyon
2024-04-15 11:42 ` Mark Wielaard
2024-04-15 12:46 ` Mark Wielaard
2024-04-15 12:56 ` Christophe Lyon
2024-04-12 20:05 ` [PATCH 5/6] autoregen.py: Add support for autogen Christophe Lyon
2024-04-12 20:05 ` [PATCH 6/6] autoregen.py: Add binutils directories to AUTORECONF_DIRS Christophe Lyon
2024-04-14 22:33 ` [PATCH 0/6] autoregen.py: Improve support for GCC Mark Wielaard
2024-04-15 11:52 ` 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=20240412200559.1649050-1-christophe.lyon@linaro.org \
--to=christophe.lyon@linaro.org \
--cc=buildbot@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).