another CONFIG_SHELL doc instance missed

[Ralf Wildenhues]

In http://thread.gmane.org/gmane.comp.sysutils.autoconf.general/5849
the move of CONFIG_SHELL to the environment of `configure' wasn't done.
In http://thread.gmane.org/gmane.comp.gnu.libtool.patches/6368 we
concluded it to be necessary though.  One instance of this was missed.

OK to apply?

Cheers,
Ralf

        * doc/install.texi (Defining Variables): Put `CONFIG_SHELL'
        in environment of `configure', not the command line.
        Reported by Howard Chu <address@hidden>.

Index: doc/install.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/install.texi,v
retrieving revision 1.43
diff -u -r1.43 install.texi
--- doc/install.texi    8 Jun 2005 07:13:50 -0000       1.43
+++ doc/install.texi    13 Jan 2006 09:37:11 -0000
@@ -226,10 +226,12 @@
 @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