Hello,
On Wed, Jun 28, 2006 at 10:20:24AM -0400, Sam Steingold wrote:
> so, obviously the configure script is being run by bash, but neither
> SHELL nor CONFIG_SHELL tell me that, so when I put
Well, CONFIG_SHELL is empty, which indicates that ./configure has
decided that the current shell is good enough and that there is no
need to search for a better one.
In that case, ./configure cannot be sure which shell it is running
under, so it trusts the variable SHELL to be set to the current
shell.
That is why it does something like
cat >config.status <<_ACEOF
#! $SHELL
...
SHELL=\${CONFIG_SHELL-$SHELL}
_ACEOF
which means that the genrated config.status contains:
#! /bin/sh
...
SHELL=${CONFIG_SHELL-/bin/sh}
And this value is also substituted later for @SHELL@.
To sum up, it seems that the root cause is an inconsistency of your
setup--it seems that you started the configure script under a shell
which did not matched the variable $SHELL in your environment.
Examples:
1) do not run
/bin/bash ./configure
run this instead:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
2) If your .profile executes /bin/bash instead of the system shell,
please remember to set SHELL correspondingly.
Hope this helps,
Stepan Kasal
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
