FYI: fix for asm.test failures on fast machines

[Alexandre Duret-Lutz]

I'm checking in this.

2002-07-04  Alexandre Duret-Lutz  <address@hidden>

        * tests/asm.test: Erase Autom4te's cache between each test.

Index: tests/asm.test
===================================================================
RCS file: /cvs/automake/automake/tests/asm.test,v
retrieving revision 1.7
diff -u -r1.7 asm.test
--- tests/asm.test      30 Jun 2002 22:44:13 -0000      1.7
+++ tests/asm.test      4 Jul 2002 15:53:22 -0000
@@ -27,6 +27,14 @@
 cat stderr
 grep AM_PROG_AS stderr
 
+# On fast machines the autom4te.cache created during the above run of
+# $AUTOMAKE is likely to have the same time stamp as the configure.in
+# created below; thus causing traces for the old configure.in to be
+# used.  We could do `sleep 2', but it's faster to erase the
+# directory.  (Erase autom4te*.cache, not autom4te.cache, because some
+# bogus installations of Autoconf use a versioned cache.)
+rm -rf autom4te*.cache
+
 # We still need CCAS.
 echo 2
 cat > configure.in << 'END'
@@ -43,6 +51,7 @@
 grep CCAS stderr
 grep AM_PROG_AS stderr
 
+rm -rf autom4te*.cache
 
 # We need CCASFLAGS.
 echo 3
@@ -61,6 +70,7 @@
 grep CCASFLAGS stderr
 grep AM_PROG_AS stderr
 
+rm -rf autom4te*.cache
 
 # We have every needed, expect a success.
 echo 4
@@ -77,6 +87,7 @@
 $ACLOCAL
 $AUTOMAKE
 
+rm -rf autom4te*.cache
 
 # We have every needed, expect a success.
 echo 5

-- 
Alexandre Duret-Lutz