[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: darwin 5.5 echo probes leaving empty SHELL
From: |
Bob Friesenhahn |
Subject: |
Re: darwin 5.5 echo probes leaving empty SHELL |
Date: |
Tue, 1 Apr 2003 17:41:07 -0600 (CST) |
I think that there is already a patch in the works for this problem.
A patch was submitted to the list which seems to work.
Bob
On Wed, 2 Apr 2003, Kevin Ryde wrote:
> On darwin 5.5, with the latest libtool and autoconf 2.57, it seems
> _LT_AC_PROG_ECHO_BACKSLASH can leave SHELL and CONFIG_SHELL set to an
> empty string. This makes config.status creation bomb, and of course
> is a bad thing overall.
>
> The echo testing gets up to fallback-echo using ORIGINAL_CONFIG_SHELL,
> but with that variable unset. The test succeeds because the configure
> script is executable and the consequent code sets SHELL and
> CONFIG_SHELL to $ORIGINAL_CONFIG_SHELL, ie. an empty string.
>
> It seems ORIGINAL_CONFIG_SHELL was not set because the system doesn't
> have a /bin/ksh, and it's only under the ksh probes that it's used.
> (I know darwin used to have /bin/sh as ksh, but on the machine I've
> got it looks like ash now.)
>
> In any case I think the fix is as simple as
>
> * libtool.m4 (_LT_AC_PROG_ECHO_BACKSLASH): Try ORIGINAL_CONFIG_SHELL
> with --fallback-echo only if that variable is set.
>
>
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen