From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Date: Tue, 31 Jan 2006 12:03:32 +0000 (+0000)
Subject: * doc/install.texi (Defining Variables): Put `CONFIG_SHELL'
X-Git-Tag: AUTOCONF-2.59c~190
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0b9bb6512ee94374dcb3c2964aad64b5bd1db497;p=thirdparty%2Fautoconf.git

* 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 77ceb5939..6ffa2043f 100644
--- 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 6d0fed74d..4ecd753e4 100644
--- 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