Hi Bruno,
This is with Automake 1.16.5 and Autoconf 2.71 on an ext4 file system.
[...]
When I add an 'rm -rf autom4te.cache' command before 'automake -a -c',
the failures disappear.
FWIW, in the Automake development sources, there is now a test to see if
autom4te is the new versio
Karl Berry wrote:
> The various test-suite.log files show different test failures each
>
> Yes. Painful. I believe this is due to a timing problem with autom4te,
> exposed by Automake using fractional second sleeps according to what the
> filesystem supports. It is fixed in the autoconf repo
Just to close this out: Bogdan worked up a patch to avoid the
fractional-second timestamps unless the new (current autoconf
development) autom4te is in used. Here is the basic change:
https://git.savannah.gnu.org/cgit/automake.git/commit/?id=b6fa73115d094c8d0da1d6759b6e7c7fca1f8a07
(also appended f
Thanks for the detailed explanations, Karl.
> I bootstrapped and installed autoconf
> from its git (as of around June 11) and have used that version with
> development automake ever since, and the timing problems have stayed gone.
I confirm that with autoconf master, automake's "make check" is re
The various test-suite.log files show different test failures each
Yes. Painful. I believe this is due to a timing problem with autom4te,
exposed by Automake using fractional second sleeps according to what the
filesystem supports. It is fixed in the autoconf repository but hasn't
been relea
