2006-02-01  Stepan Kasal  <address@hidden>

	* doc/install.texi (Defining Variables): Classify the `CONFIG_SHELL'
	hint as ``a workaround for a bug.''

Index: doc/install.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/install.texi,v
retrieving revision 1.44
diff -u -r1.44 install.texi
--- doc/install.texi	31 Jan 2006 12:03:32 -0000	1.44
+++ doc/install.texi	1 Feb 2006 17:03:30 -0000
@@ -226,17 +226,25 @@
 @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:
+
address@hidden
+Unfortunately, there is a bug in Autoconf 2.60: the command
+
address@hidden
+/bin/bash ./configure CONFIG_SHELL=/bin/bash
address@hidden example
+
address@hidden
+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