GNU bug report logs - #77852
AM_RUN_LOG not found due to ustar by default

Previous Next

Full log

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Karl Berry <karl <at> freefriends.org>
To: Ross.Burton <at> arm.com
Cc: bug-automake <at> gnu.org
Subject: Re: AM_RUN_LOG not found due to ustar by default
Date: Wed, 16 Apr 2025 15:50:00 -0600

    Is there a way to get more visibility into what autom4te is doing?

autom4te --help lists various options (at a glance: --verbose, --debug,
--trace=AM_TRY_LOG, who knows what else). I've never actually understood
autom4te in the slightest, sorry to say. Maybe best to bring it up on
bug-autoconf <at> gnu.org? Although some of the autoconf developers are here
on bug-automake, not all.

    The only failure case is when our source tree has been reconfigured
    with 1.17.0

Maybe it's a problem with autoreconf, another autoconf tool, though
admittedly that doesn't seem likely. --thanks, karl.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.