[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool: lib: command not found
From: |
Peter Rosin |
Subject: |
Re: libtool: lib: command not found |
Date: |
Fri, 05 Sep 2014 18:38:20 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 2014-09-05 17:19, address@hidden wrote:
> On Fri, Sep 05, 2014 at 05:05:52PM +0200, Peter Rosin wrote:
>> On 2014-09-05 16:52, address@hidden wrote:
>>> Hi Peter, thank you
>>>
>>> attacched the zzip config.log.
>>
>> Bleh, sorry, but could you also provide the output from
>>
>> ./libtool --config
>>
>> from your build directory?
>
> Attacched
>
> dpkg -L "*libtool*":
> libtool 2.4.2-1.10
> libtool-bin 2.4.2-1.10
Ok, this is strange.
You have this in your "libtool --config":
# Commands used to build an old-style archive.
old_archive_cmds="lib -OUT:\$oldlib\$oldobjs\$old_deplibs"
Looking in the libtool.m4 file, the only way for "lib -OUT..."
to be chosen is
if test yes = "$lt_use_gnu_ld_interface"
doesn't match.
Your "libtool --config" also has:
# Whether we are building with GNU ld or not.
with_gnu_ld="no"
which seems strange on Debian.
Looking in your config.log, I find
configure:4994: checking for ld used by i686-w64-mingw32-gcc
configure:5061: result: i686-w64-mingw32-g++-win32
configure:5068: checking if the linker (i686-w64-mingw32-g++-win32) is
GNU ld
configure:5083: result: no
which is the cause of the above strangeness. What is the output from:
i686-w64-mingw32-g++-win32 -v
Libtool assumes that GNU ld produces something that matches:
*GNU* | *'with BFD'*
Cheers,
Peter