This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: libtool: link: object name conflicts in archive
- From: Peter Rosin <peda at lysator dot liu dot se>
- To: cygwin at cygwin dot com
- Date: Wed, 16 Apr 2014 01:53:32 +0200
- Subject: Re: libtool: link: object name conflicts in archive
- Authentication-results: sourceware.org; auth=none
- References: <7c71eb34219779df3fb3d492f29bcead at mail dot eclipso dot de> <20140415093113 dot GF3271 at calimero dot vinschen dot de> <22601c400b5e0fffb54b32a9d6b2bdf8 at mail dot eclipso dot de> <20140415112757 dot GI3271 at calimero dot vinschen dot de>
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