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

Previous Next

Package: automake;

Reported by: Karl Berry <karl <at> freefriends.org>

Date: Wed, 16 Apr 2025 21:51:01 UTC

Severity: normal

Merged with 77851

To reply to this bug, email your comments to 77852 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-automake <at> gnu.org:
bug#77852; Package automake. (Wed, 16 Apr 2025 21:51:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Karl Berry <karl <at> freefriends.org>:
New bug report received and forwarded. Copy sent to bug-automake <at> gnu.org. (Wed, 16 Apr 2025 21:51:02 GMT) Full text and rfc822 format available.

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.
Merged 77851 77852. Request was from Karl Berry <karl <at> freefriends.org> to control <at> debbugs.gnu.org. (Wed, 16 Apr 2025 22:05:01 GMT) Full text and rfc822 format available.
This bug report was last modified 59 days ago.

Previous Next

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