* doc/install.texi (Compilers and Options): Weaken the

suggestion to use GNU make for VPATH builds.

diff --git a/ChangeLog b/ChangeLog
index 243187a62e9f4b804cf8ad3971339f2b87c52865..90ec2ae24319e7f993603d6502e4baa0aab553d9 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2006-06-13  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
+       * doc/install.texi (Compilers and Options): Weaken the
+       suggestion to use GNU make for VPATH builds.
+
        * lib/autom4te.in (Automake-preselections): Add AM_PROG_CXX_C_O,
        AM_PROG_F77_C_O, AM_PROG_FC_C_O, AC_FC_SRCEXT, AC_FC_FREEFORM.
 

diff --git a/doc/install.texi b/doc/install.texi
index 9b394531476892fe1ac2136a02eed51d5323a73e..5a5d1c1821d7e8063488a6feef9868ade87de49d 100644 (file)
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -104,13 +104,14 @@ Here is an example:
 
 You can compile the package for more than one kind of computer at the
 same time, by placing the object files for each architecture in their
-own directory.  To do this, you should use @acronym{GNU} @command{make}.
+own directory.  To do this, you can use @acronym{GNU} @command{make}.
 @command{cd} to the directory where you want the object files and
 executables to go and run the @command{configure} script.
 @command{configure} automatically checks for the source code in the
 directory that @command{configure} is in and in @file{..}.
 
-With a non-@acronym{GNU} @command{make}, you should compile the package for one
+With a non-@acronym{GNU} @command{make},
+it is safer to compile the package for one
 architecture at a time in the source code directory.  After you have
 installed the package for one architecture, use @samp{make distclean}
 before reconfiguring for another architecture.