|
From: | Paul Eggert |
Subject: | Re: autoconf-2.72d on CentOS 8: testsuite: 11 failed |
Date: | Fri, 1 Dec 2023 15:35:40 -0800 |
User-agent: | Mozilla Thunderbird |
On 2023-12-01 08:18, Bruno Haible wrote:
Zack Weinberg wrote:
...
2023-12-01+08:27:37.7201689730 configure 2023-12-01+08:27:39.8531823020 autom4te.cache/requests
...
2023-12-01+06:44:03.2893079030 stderr-raw 2023-12-01+06:44:05.4383178570 configure 2023-12-01+06:44:05.4393178610 autom4te.cache/requests
A difference between Zack's good output and your bad output is that Zack's build did not rebuild configure (it's two seconds older than autom4te.cache/requests) but yours did.
I'm not sure exactly what's going wrong. Part of the problem is that I suspects later actions by the bad 'configure' overwrote some timestamps that were treated incorrectly.
In reading the code it's clear that it's confused about timestamps in this area as it is using the maximum of two timestamps when it should be using the minimum. I installed the attached patch, which fixes that bug. However, I don't know whether that will address the problem you observed.
0001-Be-more-conservative-about-cache-timestamps.patch
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |