* Paul Eggert wrote on Thu, Jan 27, 2005 at 06:35:57PM CET:
> Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> writes:
>
> > This would require the user to issue
> > CONFIG_SHELL=/bin/foosh /bin/foosh ./configure
> >
> > or the m4sh setup to do some (possibly unnecessary) re-execution.
> >
> > Now I know current Autoconf docs do not specify above use, but users
> > imply it, and Libtool would benefit from a solution to this.
> > There, one problem is that $ECHO is computed for the shell run at
> > configure time, but that value might not be valid for $CONFIG_SHELL.
> >
> > What do you think is more appropriate: another exec or a doc update?
>
> It might not hurt to do both. The doc fix would be easier, so let's
> start with that; maybe it's enough.
How about this?
* doc/autoconf.texi (config.status Invocation), doc/install.texi
(Defining Variables): Describe how to run `configure' and
subsequent scripts under a specific shell.
Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.867
diff -u -r1.867 autoconf.texi
--- doc/autoconf.texi 24 Jan 2005 12:24:02 -0000 1.867
+++ doc/autoconf.texi 29 Jan 2005 14:31:09 -0000
@@ -13628,6 +13628,11 @@
The shell with which to run @command{configure} for the @option{--recheck}
option. It must be Bourne-compatible. The default is a shell that
supports @env{LINENO} if available, and @file{/bin/sh} otherwise.
+Note that setting @var{CONFIG_SHELL} might not be sufficient if you run
+@command{configure} directly (@pxref{Defining Variables}).
+@example
+
+@end example
@end defvar
@defvar CONFIG_STATUS
Index: doc/install.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/install.texi,v
retrieving revision 1.41
diff -u -r1.41 install.texi
--- doc/install.texi 20 Aug 2004 19:58:07 -0000 1.41
+++ doc/install.texi 29 Jan 2005 14:31:09 -0000
@@ -226,6 +226,15 @@
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
+If you need @command{configure} as well as subsequent scripts like
+@command{config.status} to be executed by a certain shell, then set
+@var{CONFIG_SHELL} and use @command{configure} as argument to the shell:
+
+@example
+CONFIG_SHELL=/usr/bin/bash /usr/bin/bash ./configure [...]
+@end example
+
+@xref{config.status Invocation}, for more details.
@node configure Invocation
@section @command{configure} Invocation
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
