Follow-up Comment #2, sr#110986 (group autoconf):
This is a regression caused by commit
<https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=713d9822bbfb2923115065efaefed34a0113f8a1>,
"Fix timing bug on high-speed builds". That commit changed autom4te's logic
for deciding whether its output file is newer than its cache file: if their
modification times are equal, the output is considered out of date. Since
both files are created in quick succession, on file systems with coarse
timestamps (1 or 2s resolution), it is very easy for their modification times
to be equal.
For 2.72 I'm going to make the test suite adjust the modification time of the
file that's supposed to be newer, but I'm also going to leave this bug open,
because autom4te _ought_ to be able to ensure that the cache file is always
observed to be older than the output.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110986>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
