The INSTALL wording mentioned Autoconf 2.60 and made a promise; I'd
rather not make promises and 2.60 is not the only Autoconf with the
problem. I installed this to tighten things up a bit.
2006-02-12 Paul Eggert <[EMAIL PROTECTED]>
* doc/install.texi (Defining Variables): Tighten up the
CONFIG_SHELL wording.
--- doc/install.texi 4 Feb 2006 14:10:46 -0000 1.45
+++ doc/install.texi 13 Feb 2006 07:59:10 -0000 1.46
@@ -5,8 +5,8 @@
@unnumbered Installation Instructions
-Copyright @copyright{} 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005
-Free Software Foundation, Inc.
+Copyright @copyright{} 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004,
+2005, 2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
@@ -228,24 +228,14 @@ causes the specified @command{gcc} to be
overridden in the site shell script).
@noindent
-Unfortunately, there is a bug in Autoconf 2.60: the command
-
[EMAIL PROTECTED]
-/bin/bash ./configure CONFIG_SHELL=/bin/bash
[EMAIL PROTECTED] example
-
[EMAIL PROTECTED]
-doesn't work as it should. A possible workaround is to set the variable in
-the environment, too:
+Unfortunately, this technique does not work for @env{CONFIG_SHELL} due
+to an Autoconf bug. Until the bug is fixed you can use this
+workaround:
@example
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
@end example
[EMAIL PROTECTED]
-This problem will be fixed in a future release of Autoconf.
-
-
@node configure Invocation
@section @command{configure} Invocation
