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

Message received at submit <at> debbugs.gnu.org:

Received: (at submit) by debbugs.gnu.org; 16 Apr 2025 20:57:05 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Wed Apr 16 16:57:04 2025
Received: from localhost ([127.0.0.1]:43213 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1u59oa-00085Z-Vp
	for submit <at> debbugs.gnu.org; Wed, 16 Apr 2025 16:57:04 -0400
Received: from lists.gnu.org ([2001:470:142::17]:53674)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <karl@HIDDEN>)
 id 1u59oN-000843-A4
 for submit <at> debbugs.gnu.org; Wed, 16 Apr 2025 16:56:51 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <karl@HIDDEN>)
 id 1u59oH-0000bR-S4
 for bug-automake@HIDDEN; Wed, 16 Apr 2025 16:56:41 -0400
Received: from frenzy.freefriends.org ([198.99.81.75] helo=freefriends.org)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <karl@HIDDEN>)
 id 1u59oG-0002K8-9x
 for bug-automake@HIDDEN; Wed, 16 Apr 2025 16:56:41 -0400
X-Envelope-From: karl@HIDDEN
Received: from freefriends.org (localhost [127.0.0.1])
 by freefriends.org (8.16.1/8.16.1) with ESMTPS id 53GKuYBO1140343
 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT);
 Wed, 16 Apr 2025 14:56:34 -0600
Received: (from apache@localhost)
 by freefriends.org (8.16.1/8.14.7/Submit) id 53GKuYmn1140342;
 Wed, 16 Apr 2025 14:56:34 -0600
Date: Wed, 16 Apr 2025 14:56:34 -0600
Message-Id: <202504162056.53GKuYmn1140342@HIDDEN>
From: Karl Berry <karl@HIDDEN>
To: Ross.Burton@HIDDEN
Subject: AM_RUN_LOG not found due to ustar by default
Received-SPF: pass client-ip=198.99.81.75; envelope-from=karl@HIDDEN;
 helo=freefriends.org
X-Spam_score_int: -41
X-Spam_score: -4.2
X-Spam_bar: ----
X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3,
 RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001,
 SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: submit
Cc: bug-automake@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi Ross - continuing on bug-automake from your report at
https://lists.gnu.org/archive/html/automake/2025-04/msg00002.html.
(No reason to bother platform-testers with this.)

    > I repeated my tests and rebuilds of existing source trees that have
    > been configured with 1.70 still break for me:

As expected, since I didn't make any changes to fix it, since we could
never reproduce your breakage.

    Reverting 2d2ff6070ca13428032c14f1d1cfd57b6b22e42d (use ustar by
    default) makes this go away.

Yes, also as expected. But we have to find out why.

    1. build intltool out-of-tree from a fresh tarball with automake 1.17.0

Where did you get this intltool, precisely? Not that it's likely to
matter, granted, but for purposes of reproducing ...

    1. build intltool out-of-tree from a fresh tarball with automake 1.17.0
    2. delete the build tree, autoreconf the same source tree with 1.17.92

Although the automake change is provoking the bug, I think a crucial
question is what version of autoconf you are using, not
automake. Because autom4te is part of autoconf, not automake, as we
previously discussed. Thus I suggest trying with the latest released
autoconf, 2.72, from
https://ftp.gnu.org/gnu/autoconf/autoconf-2.72.tar.xz.

As I recall, you were using an autoconf development version from
git. Maybe that is the culprit. Otherwise, it continues to be strange
that no one else has reported or can reproduce the problem.

As I wrote before, all I can think of is for you to make a tarball of
your source tree, including autom4te.cache, after each step. Then, if
we're starting from (supposedly) the same source, and running
(supposedly) the same versions of the autotools, we should be able to
see at what point they diverge.

Also, what happens if you build from the start with 1.17.92? (I.e., no
autoreconf involved.) Does it find AM_TRY_LOG?

Best,
Karl