* doc/install.texi (Defining Variables): Put `CONFIG_SHELL'

in environment of `configure', not the command line.
Reported by Howard Chu <hyc@highlandsun.com>.

diff --git a/ChangeLog b/ChangeLog
index 77ceb5939239fc781495aa5657d2ba75dfb6b90a..6ffa2043f5279ea7e7cb2f0ce1233cc577f01543 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2006-01-31  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
+
+       * doc/install.texi (Defining Variables): Put `CONFIG_SHELL'
+       in environment of `configure', not the command line.
+       Reported by Howard Chu <hyc@highlandsun.com>.
+
 2006-01-25  Paul Eggert  <eggert@cs.ucla.edu>
 
        * doc/autoconf.texi (Limitations of Builtins): Document the

diff --git a/doc/install.texi b/doc/install.texi
index 6d0fed74d338b6dbff82726ed494c94b4c27e9e5..4ecd753e431314db723a6b0ad79eb8f84a6c9215 100644 (file)
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -226,10 +226,12 @@ For example:
 @noindent
 causes the specified @command{gcc} to be used as the C compiler (unless it is
 overridden in the site shell script).
-Here is a another example:
+Because the value of @var{CONFIG_SHELL} may be needed before the argument
+parsing loop of @command{configure}, it is an exception to this rule, and
+should be put in the environment:
 
 @example
-/bin/bash ./configure CONFIG_SHELL=/bin/bash
+CONFIG_SHELL=/bin/bash /bin/bash ./configure
 @end example
 
 @noindent