[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CONFIG_SHELL behavior

From: Paul Eggert
Subject: Re: CONFIG_SHELL behavior
Date: Mon, 31 Jan 2005 16:37:15 -0800
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Thanks for the patch.  I shortened it a bit, removed an undesirable
cross-reference out of INSTALL, and then installed this:

2005-01-31  Paul Eggert  <address@hidden>

        * doc/autoconf.texi (config.status Invocation): Warn about
        discrepancy between CONFIG_SHELL and shell used to invoke 'configure'.
        * doc/install.texi (Defining Variables): Likewise.
        Based on a proposed patch by Ralf Wildenhues.

--- autoconf.texi       28 Jan 2005 21:55:57 -0000      1.868
+++ autoconf.texi       1 Feb 2005 00:36:24 -0000       1.870
@@ -13628,6 +13628,10 @@ can alter its behavior:
 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.
+Invoking @command{configure} by hand bypasses this setting, so you may
+need to use a command like @samp{/bin/bash ./configure
+CONFIG_SHELL=/bin/bash} to insure that the same shell is used
 @end defvar
--- install.texi        20 Aug 2004 19:58:07 -0000      1.41
+++ install.texi        1 Feb 2005 00:28:05 -0000
@@ -225,7 +225,14 @@ For example:
 will cause the specified gcc to be used as the C compiler (unless it is
 overridden in the site shell script).
+Here is a another example:
+/bin/bash ./configure CONFIG_SHELL=/bin/bash
address@hidden example
+The @samp{CONFIG_SHELL=/bin/bash} operand will cause subsequent
+configuration-related scripts to be executed by @command{/bin/bash}.
 @node configure Invocation
 @section @command{configure} Invocation

reply via email to

[Prev in Thread] Current Thread [Next in Thread]