DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Kl7X+40EJsSZOwT7dAzHqV4LEsElG/NgA6b3+K1ekkr
	dBRC/wq+UIFilRK1So/HIEFZHp44kvDLrL7hBSbzEQ0etdhPihv4bGHAbS8Ph80u
	d7jpShl3gyPvY9zI+cz9bqiwVpIsZ5F2N2e9F5oZm+uE6p4lq32YZvbOLlRLo0Xo
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <534DC67C.3080909@lysator.liu.se>
Date: Wed, 16 Apr 2014 01:53:32 +0200
From: Peter Rosin <peda@lysator.liu.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: libtool: link: object name conflicts in archive
References: <7c71eb34219779df3fb3d492f29bcead@mail.eclipso.de> <20140415093113.GF3271@calimero.vinschen.de> <22601c400b5e0fffb54b32a9d6b2bdf8@mail.eclipso.de> <20140415112757.GI3271@calimero.vinschen.de>
In-Reply-To: <20140415112757.GI3271@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 2014-04-15 13:27, Corinna Vinschen wrote:
> On Apr 15 11:16, Gisela Haschmich wrote:
>>>> Hello,
>>>>
>>>> i tried to compile MBDyn 1.5.5 with cygwin and got an error "libtool:
>>> link: object name conflicts in archive". I used the same for 1.5.0 and
>>> it worked.
>>>>
>>
>>>> libtool: link: object name conflicts in archive: .libs/libmbwrap.lax/liby12.lib//home/ntmoe/mbdyn-1.5.5/libraries/liby12/.libs/liby12.lib
>>
>>>>
>>>> i found with google, that it could be an error with path variable, because
>>> it needs lib.exe from Visual Studio. I changed it to minimal, but i have
>>> still the same error
>>>
>>> No, it doesn't.  Libtool calls gcc, it never tries to use VS tools.
>>> This looks like a problem earlier in the build.
>>>
>> and whats about lib.exe, do i need the path to VS tools lib.exe or what should use instead ?
> 
> gcc uses ld from binutils.  There's really no reason to have any VC tool
> in the path.

Side note, the GNU "equivalent" of MS lib.exe is ar. (ld corresponds to
MS link.exe).

Regarding the issue, it is a bad sign that the archives are named libmbmath.lib,
libmbutil.lib etc. For a Cygwin build, you want them named libmbmath.a. The
.lib suffix is a clear indicator of a problem earlier in the build, just
like Corinna said. Is the Cygwin binutils package installed properly? I
imagine something like this could happen if the binutils install is broken
and the Microsoft tools are on $PATH (but I haven't tested that).

Cheers,
Peter


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple