From: Jim Meyering Date: Sat, 3 Nov 2007 18:17:32 +0000 (+0100) Subject: Adjust the build procedure so "make check" works reliably. X-Git-Tag: v2.62~167 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8b5560fc0753a3fa1333619972ba87157784a739;p=thirdparty%2Fautoconf.git 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 d6b4ba1e..d1eece0e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2007-11-03 Jim Meyering + 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 32c4a476..61616fea 100644 --- 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,