From: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue, 6 Jun 2006 06:18:40 +0000 (+0000)
Subject: * NEWS: Don't blame non-GNU VPATH compatibility issues on Automake.
X-Git-Tag: AUTOCONF-2.60~40
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8d3239f506f8453bb79f09d03ba4c499671f4fd9;p=thirdparty%2Fautoconf.git

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

diff --git a/ChangeLog b/ChangeLog
index d607f3a3b..9b0b0aaa3 100644
--- 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 b8b498e3d..12579e55c 100644
--- 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.