Hello Ralf,

On Fri, Jan 13, 2006 at 10:37:09AM +0100, Ralf Wildenhues wrote:
>         * doc/install.texi (Defining Variables): Put `CONFIG_SHELL'
>         in environment of `configure', not the command line.
...
> OK to apply?

a quick answer: why is it necessary to have this?

It seems that the problem could be fixed by inspecting the arguments
before the echo tests, so that CONFIG_SHELL is set correctly.

But I guess that there must be better solution:
1) cannot libtool use something like AS_DETECT_SUGGESTED if it is
going to exec configure under a "better shell"?
2) or if the main purpose is to find out a good shell for the libtool
scripts, perhaps the tests could be performed later...

3) libtool (mis)uses the [NOTICE] divertion from m4sh (which is there
only because of libtool ;-).  Shouldn't we better specify this
communication, and find an adequate interface.

Please don't thing about compatibility with old version for now.
Let's find a good specification first; then we can do some hacks to
fix for combinations of different versions.

Have a nice day,
        Stepan Kasal


Reply via email to