README-hacking, and GNUmakefile/PATH-export pushed

[Jim Meyering]

As discussed, here are the two patches I've just pushed:

>From f4208c7aa9ba5e95ca7746ce0bd307bb8553b3b8 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sat, 3 Nov 2007 10:27:02 +0100
Subject: [PATCH] Use just-built tools, when possible.

* GNUmakefile (PATH): Set and export here, ...
(dummy): ... rather than here.

Signed-off-by: Jim Meyering <address@hidden>
---
 ChangeLog   |    6 ++++++
 GNUmakefile |    5 ++++-
 2 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 9ba94b5..d6b4ba1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2007-11-03  Jim Meyering  <address@hidden>
+
+       Use just-built tools, when possible.
+       * GNUmakefile (PATH): Set and export here, ...
+       (dummy): ... rather than here.
+
 2007-11-03  Ralf Wildenhues  <address@hidden>
        and Andreas Schwab  <address@hidden>

diff --git a/GNUmakefile b/GNUmakefile
index 8dcefc5..79ad492 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -38,6 +38,9 @@ ifeq ($(have-Makefile),yes)
 # Make tar archive easier to reproduce.
 export TAR_OPTIONS = --owner=0 --group=0 --numeric-owner

+# Build with our own versions of these tools, when possible.
+export PATH = '$(shell echo "`pwd`/tests:$$PATH")'
+
 include Makefile

 # Ensure that $(VERSION) is up to date for dist-related targets, but not
@@ -48,7 +51,7 @@ ifeq (0,$(MAKELEVEL))
     _curr-ver := $(shell build-aux/git-version-gen .version)
     ifneq ($(_curr-ver),$(VERSION))
       $(info INFO: running autoreconf for new version string: $(_curr-ver))
-      dummy := $(shell rm -rf autom4te.cache; PATH=`pwd`/tests:$$PATH; 
autoreconf -i)
+      dummy := $(shell rm -rf autom4te.cache; autoreconf -i)
     endif
   endif
 endif
--
1.5.3.5.529.ge3d6d


>From 8b5560fc0753a3fa1333619972ba87157784a739 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sat, 3 Nov 2007 19:17:32 +0100
Subject: [PATCH] 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.

Signed-off-by: Jim Meyering <address@hidden>
---
 ChangeLog      |    4 ++++
 README-hacking |    7 +++++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index d6b4ba1..d1eece0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2007-11-03  Jim Meyering  <address@hidden>

+       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 32c4a47..61616fe 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,
--
1.5.3.5.529.ge3d6d