Since we fixed autoconf/lib/autom4te.cfg in Autoconf 2.60, now when we
call $ACLOCAL, the traces that were created by the $AUTOCONF before are
sufficient; and since they appear with the same time stamp as all known
input files to aclocal.m4, they are used by autom4te. So we have to
tell the autom4te invoked by aclocal that it has to do work.
The following $AUTOCONF should not need --force: it will know by way of
the updated autom4te/output.x file.
Does this make the failures go away?
Cheers,
Ralf
* tests/acloca20.test: Use `autom4te --force' with aclocal,
to force update on fast machines where the previous autoconf
invocation happened within the same second.
Report by Greg Schafer.
Index: tests/acloca20.test
===================================================================
RCS file: /cvs/automake/automake/tests/acloca20.test,v
retrieving revision 1.1
diff -u -r1.1 acloca20.test
--- tests/acloca20.test 19 Mar 2006 05:09:11 -0000 1.1
+++ tests/acloca20.test 24 Oct 2006 12:24:46 -0000
@@ -51,7 +51,7 @@
sed 's/dnl //' <configure.in >configure.int
mv -f configure.int configure.in
-$ACLOCAL
+AUTOM4TE="${AUTOM4TE-autom4te} --force" $ACLOCAL
$AUTOCONF
./configure | grep 'right foo'
grep 'wrong foo' foo.m4
