bug-libtool
[Top][All Lists]
Advanced

[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 05:28:09 +0200
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

Hello Bob, Gary,

* Bob Friesenhahn wrote on Mon, May 05, 2008 at 01:05:41AM CEST:
> On Sun, 4 May 2008, Gary V. Vaughan wrote:
>>> and running in verbose mode reveals that this error is occuring:
>>>
>>> /tests/demo --prefix=/scratch/bfriesen/build/libtool-2.2.4/_inst  
>>> --disable-shared
>>> configure: error: Working directory cannot be determined
>>
>> I'd say that's a '$PWD fork reduction patch' bug :-(

Most certainly not.  That patch never even made it into the tree yet.
And if it did, it would affect the libtool and libtoolize scripts,
but not the configure script.

Bob, how did you configure?  If you set CONFIG_SHELL, you need to
  CONFIG_SHELL=/bin/dash
  export CONFIG_SHELL
  $CONFIG_SHELL ./configure ...

as documented in INSTALL.  For me, that works with 2.2.4 and generates
no failures on GNU/Linux.  Please provide more details, show the output
of configure and make and maybe even verbose make check (suffices for a
couple of failed tests).

> Yes.  I expect that it is related to the 'dash' + 'make -C dir' bug that 
> we discussed in private.

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.

Cheers,
Ralf




reply via email to

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