[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool 2.2.4 test failures with 'dash'
From: |
Ralf Wildenhues |
Subject: |
Re: libtool 2.2.4 test failures with 'dash' |
Date: |
Tue, 6 May 2008 08:34:53 +0200 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
* Bob Friesenhahn wrote on Tue, May 06, 2008 at 06:07:37AM CEST:
> On Tue, 6 May 2008, Ralf Wildenhues wrote:
>>
>> Bob, how did you configure? If you set CONFIG_SHELL, you need to
>> CONFIG_SHELL=/bin/dash
>> export CONFIG_SHELL
>> $CONFIG_SHELL ./configure ...
>
> I had CONFIG_SHELL exported in the environment. Accidentally this time.
> :-)
So that was the problem, that you set CONFIG_SHELL but did not use it to
invoke configure.
> I believe that CONFIG_SHELL exported in the parent environment is more
> weighty (far reaching) than $CONFIG_SHELL ./configure.
Well, it's not what INSTALL currently demands.
>> Dunno what you're refering to here, but "make -C" is not portable to
>> non-GNU make, and if we use that anywhere in Libtool, that is a bug.
>
> I am referring to the issue we discussed before you went on break where
> 'gmake' (GNU make) in the vpathed build tree works, but not 'gmake -C
> /path/to/build/tree'. The C parts work, but not C++ due to an apparent
> insufficiently-qualified path. This also happens with 'dash' on my
> system but not with 'bash'.
I need to see reproducible failures or at least verbose output,
because I fail to parse your description. Sorry.
Cheers,
Ralf