* NEWS: Don't blame non-GNU VPATH compatibility issues on Automake.

diff --git a/ChangeLog b/ChangeLog
index d607f3a3b76ffaf748a80c73d77db423a8c2b966..9b0b0aaa3c3e069c6da32a827479a17128592099 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2006-06-05  Paul Eggert  <eggert@cs.ucla.edu>
 
+       * NEWS: Don't blame non-GNU VPATH compatibility issues on Automake.
+
        * doc/autoconf.texi (Integer Overflow): Mention that INT_MIN % -1
        typically overflows on x86 CPUs, even though the C standard
        requires otherwise.

diff --git a/NEWS b/NEWS
index b8b498e3d6af3d3ae04d8491325818af3dba7d22..12579e55caeb889b848e9c4701b1a236eece7c71 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -8,9 +8,9 @@
   INSTALL now suggests VPATH builds (e.g., "sh ../srcdir/configure")
   only if you use GNU make.  In practice, other 'make' implementations
   have too many subtle incompatibilities in their support for VPATH.
-  These incompatibilities do not hurt bare Autoconf, but do affect
-  Automake-generated makefiles.  Recommending GNU make keeps the
-  installation instructions simpler.
+  Many packages (including Autoconf itself) are portable to other
+  'make' implementations, but some packages are not, and recommending
+  GNU make keeps the installation instructions simpler.
 
 ** Even more safety checks for the new Directory variables:
   Warn about suspicious `${datarootdir}' found in config files output.