Re: CONFIG_SHELL behavior

[Paul Eggert]

Ralf Wildenhues <address@hidden> 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.