[Top][All Lists]

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

Re: bison-1.29c 'configure' problems on Solaris 8.

From: Paul Eggert
Subject: Re: bison-1.29c 'configure' problems on Solaris 8.
Date: Thu, 4 Oct 2001 12:23:42 -0700 (PDT)

> From: Akim Demaille <address@hidden>
> Date: 04 Oct 2001 17:38:43 +0200
> some of our parts would be extremely happy to have as good
> a shell as possible.  For instance it would help Libtool which needs a
> good `echo'.

Could you give more details about this?  What 'echo' features does
Libtool need, other than those features standardized by POSIX?

> From: Akim Demaille <address@hidden>
> Date: 04 Oct 2001 17:46:36 +0200
>         Still, I don't understand why we don't loop over shells and
>         then on PATH instead of the converse.

Because it is the wrong strategy if one wants to replace "#!/bin/sh"
with "address@hidden@" on Solaris 8.  If you loop on PATH first, you may get
SHELL="/usr/xpg4/bin/sh", or even SHELL="/user/eggert/bin/sh".  Both
of these solutions are inferior to "/bin/bash", which is more likely
to be present on all hosts in the installation, and which is what the
current code produces.

If I recall correctly, I originally wrote the code to loop on the
shell first, and then went to the current solution when I ran into
problems like the above.

This is one area that we can't hope to fully automate on all hosts, as
each installer will have different opinions on what is "nice" shell is.
The best that we can do is to come up with a reasonable heuristic that
works well enough in practice, with an override mechanism for experts
who know better.

reply via email to

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