Call the CONFIG_SHELL hint a workaround.

diff --git a/ChangeLog b/ChangeLog
index f8c4f12949cc9f7041aefd2150d47ad4176f6954..a4b4ea8723bd8958ab604b0618b0faa6404e5452 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2006-02-04  Stepan Kasal  <kasal@ucw.cz>
+
+       * doc/install.texi (Defining Variables): Classify the `CONFIG_SHELL'
+       hint as ``a workaround for a bug.''
+
 2006-01-31  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
        * bin/autoreconf.in: New option `--no-recursive'.

diff --git a/doc/install.texi b/doc/install.texi
index 4ecd753e431314db723a6b0ad79eb8f84a6c9215..0e6e444ad4f1ae3b4d9076a3d65fbd623bf0c0a1 100644 (file)
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -226,17 +226,25 @@ For example:
 @noindent
 causes the specified @command{gcc} to be used as the C compiler (unless it is
 overridden in the site shell script).
-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:
+
+@noindent
+Unfortunately, there is a bug in Autoconf 2.60: the command
+
+@example
+/bin/bash ./configure CONFIG_SHELL=/bin/bash
+@end example
+
+@noindent
+doesn't work as it should.  A possible workaround is to set the variable in
+the environment, too:
 
 @example
-CONFIG_SHELL=/bin/bash /bin/bash ./configure
+CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
 @end example
 
 @noindent
-Here the @samp{CONFIG_SHELL=/bin/bash} operand causes subsequent
-configuration-related scripts to be executed by @command{/bin/bash}.
+This problem will be fixed in a future release of Autoconf.
+
 
 @node configure Invocation
 @section @command{configure} Invocation