Weird instability of automake-1.15.1

Weird instability of automake-1.15.1

[Martin Liška]

Hi.

I see a weird behavior when I run:
AUTOCONF=autoconf-2.69 ~/bin/automake-1.15.1/bin/automake

in one of my gcc git repos:

$ ~/Programming/gcc/gotools> AUTOCONF=autoconf-2.69 ~/bin/automake-1.15.1/bin/automake
$ git diff | cat

(no output)

However, if I clone a fresh repo I see:

$ git clone git://gcc.gnu.org/git/gcc.git --depth=1
$ cd gotools/
$ AUTOCONF=autoconf-2.69 ~/bin/automake-1.15.1/bin/automake
$ git diff | cat
diff --git a/gotools/Makefile.in b/gotools/Makefile.in
index 2783b91ef..9739a7952 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 \

Can please anybody reproduce that? I've also tried touching all files in my original repo,
but still, no change.

Cheers,
Martin

Re: Weird instability of automake-1.15.1

[Andreas Schwab]

On Aug 31 2022, Martin Liška wrote:

> Can please anybody reproduce that? I've also tried touching all files in my original repo,
> but still, no change.

Probably a bug in automake, it oscillates between the two states in a
random way.  The contents of autom4te.cache/requests also changes each
time.  My guess would be unstable hashing.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."