Adjust the build procedure so "make check" works reliably.

* README-hacking: Include an extra step between "make" and
"make check" to ensure that the latter passes.

diff --git a/ChangeLog b/ChangeLog
index d6b4ba1e67ff1efc91dad0d8a0dc977ec6a63e88..d1eece0e95675c4c8183282c169d2cd035177e9f 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2007-11-03  Jim Meyering  <meyering@redhat.com>
 
+       Adjust the build procedure so "make check" works reliably.
+       * README-hacking: Include an extra step between "make" and
+       "make check" to ensure that the latter passes.
+
        Use just-built tools, when possible.
        * GNUmakefile (PATH): Set and export here, ...
        (dummy): ... rather than here.

diff --git a/README-hacking b/README-hacking
index 32c4a4766d3a60b6f495fdfb11a1fe5417b0fcad..61616feafb0709d95607f96c8cdacb393c7a467c 100644 (file)
--- a/README-hacking
+++ b/README-hacking
@@ -33,12 +33,15 @@ You can get a copy of the source repository like this:
 The next step is to generate files like configure and Makefile.in:
 
        $ cd autoconf
-       $ ( PATH=`pwd`/tests:$PATH; autoreconf -vi )
+       $ autoreconf -vi
 
-And there you are!  Just
+Since we're building autoconf itself, and its tests are picky, the
+following procedure includes an extra step to ensure that some
+generated files are regenerated using the tools just build by "make":
 
        $ ./configure
        $ make
+       $ ( PATH=`pwd`/tests:$PATH; autoreconf -vi )
        $ make check
 
 At this point, there should be no difference between your local copy,