From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@linaro.org>, buildbot@sourceware.org
Cc: Thomas Schwinge <tschwinge@baylibre.com>
Subject: Re: [PATCH 4/6] autoregen.py: Use autoreconf in most GCC directories
Date: Mon, 15 Apr 2024 13:42:31 +0200 [thread overview]
Message-ID: <a3fa86e2d9fe19c15a61790964bf3cc3c90303fd.camel@klomp.org> (raw)
In-Reply-To: <20240412200559.1649050-5-christophe.lyon@linaro.org>
Hi,
On Fri, 2024-04-12 at 20:05 +0000, Christophe Lyon wrote:
> Add most of GCC's subdirectories to AUTORECONF_DIRS, since 'autoreconf
> -f' works for them.
> [...]
> # these directories are known to can be re-generatable with a simple autoreconf
> # without special -I flags
> AUTORECONF_DIRS = [
> + # binutils-gdb subdirs
> "gdb",
> "gdbserver",
> "gdbsupport",
> "gnulib",
> +
> + # gcc subdirs
> + "c++tools", # No aclocal.m4
> + #"gcc", # No Makefile.am
> + #"fixincludes", # autoreconf complains about GCC_AC_FUNC_MMAP_BLACKLIST
> + "gnattools", # No aclocal.m4
> + "gotools",
Oddly this now generates:
https://builder.sourceware.org/buildbot/#/builders/269/builds/4325
Entering directory /home/builder/shared/bb3/worker/gcc-
autoregen/build/gnattools
+ autoreconf-2.69 -f
[... where before it was just autoconf-2.69 -f ...]
diff --git a/gotools/Makefile.in b/gotools/Makefile.in
index 36c2ec2abd3..f40883c39be 100644
--- a/gotools/Makefile.in
+++ b/gotools/Makefile.in
@@ -704,8 +704,8 @@ distclean-generic:
maintainer-clean-generic:
@echo "This command is intended for maintainers to use"
@echo "it deletes files that may require special tools to
rebuild."
-@NATIVE_FALSE@install-exec-local:
@NATIVE_FALSE@uninstall-local:
+@NATIVE_FALSE@install-exec-local:
clean: clean-am
clean-am: clean-binPROGRAMS clean-generic clean-noinstPROGRAMS \
This started with:
https://gcc.gnu.org/cgit/gcc/commit/?id=f7c8fa7280c85cbdea45be9c09f36123ff16a78a
Inline 'gcc/rust/Make-lang.in:RUST_LDFLAGS' into single user
gcc/rust/
* Make-lang.in (RUST_LDFLAGS): Inline into single user.
Which doesn't really make sense, since that doesn't touch gotools at
all...
I am not sure why.
Cheers,
Mark
next prev parent reply other threads:[~2024-04-15 11:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 20:05 [PATCH 0/6] autoregen.py: Improve support for GCC Christophe Lyon
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 [this message]
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=a3fa86e2d9fe19c15a61790964bf3cc3c90303fd.camel@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=tschwinge@baylibre.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).