That patch looks good to me, except:
> + CONFIG_SHELL=$SHELL exec $SHELL $[0] $ac_configure_args
> \$ac_configure_extra_args --no-create --no-recursion
Many shells treat "A=B exec COMMAND" differently; they ignore the
assignment. For example, ksh M-11/16/88i, or Solaris 10 /bin/sh.
I suspect t
Hi Paul,
* Paul Eggert wrote on Mon, Nov 07, 2005 at 03:11:26AM CET:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > One possibility would be to restart once with /bin/sh, or, if part of
> > the environment, with CONFIG_SHELL, or, after parsing the command line,
> > with CONFIG_SHELL, if that
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> One possibility would be to restart once with /bin/sh, or, if part of
> the environment, with CONFIG_SHELL, or, after parsing the command line,
> with CONFIG_SHELL, if that is given there. All of this is very slow
> (read: dog-slow), and I'd really li
The Libtool issue described here may need cooperation from Autoconf.
In libtool.m4's _LT_PROG_ECHO_BACKSLASH, we search for a good
combination of an `echo' program (that does not interpret backslashes)
and a $SHELL that also qualifies for _AS_DETECT_BETTER_SHELL.
This detection has one, or rather
