Hi Ross - back on this: | configure:2612: error: possibly undefined macro: AM_RUN_LOG
What version of autoconf are you using? If it's not the original GNU Autoconf 2.72, maybe you could try that? That's what I'm using. I'm guessing Nick is either using that or the current autoconf sources from git. Failing that, all I can think of is to make a tarball of the entire source dir, including the autom4te.cache directory, after each step as shown by Nick below, so we can see where your results begin to differ from ours. Thanks, Karl Date: Fri, 28 Feb 2025 20:09:47 -0500 From: Nick Bowler <nbow...@draconx.ca> To: Ross Burton <ross.bur...@arm.com> Cc: Karl Berry <k...@freefriends.org>, "automake@gnu.org" <automake@gnu.org> Subject: Re: automake-1.17.90 pretest released [alpha] On Thu, Feb 27, 2025 at 06:23:42PM +0000, Ross Burton wrote: .. > > | configure:2612: error: possibly undefined macro: AM_RUN_LOG .. > A leaner test case is icon-naming-utils. If I build that with > automake 1.17.0, it works. If I build it _from clean_ with 1.17.90, > it works. > > If I build it with 1.17.0 and then autoreconf with 1.17.90, it fails. > Really mysteriously the generated aclocal.m4 has been regenerated > (because the copyright dates are different) but it is missing the > AM_RUN_LOG macro. I have a package icon-naming-utils-0.8.90.tar.gz and I cannot reproduce such a failure either... % gunzip -c icon-naming-utils-0.8.90.tar.gz | tar xf - % cd icon-naming-utils-0.8.90 % PATH=/path/to/automake-1.17/bin:$PATH autoreconf --force --install [no errors] % ./configure [no errors] % PATH=/path/to/automake-1.17.90/bin:$PATH autoreconf [no errors] % ./configure [no errors] % grep 'DEFUN.*AM_RUN_LOG' aclocal.m4 AC_DEFUN([AM_RUN_LOG], So hard to say what might be going on... is there something you're doing differently? Cheers, Nick
