From: Peter Rosin <peda@lysator.liu.se>
To: cygwin@cygwin.com
Subject: Re: libtool: link: object name conflicts in archive
Date: Tue, 15 Apr 2014 23:53:00 -0000 [thread overview]
Message-ID: <534DC67C.3080909@lysator.liu.se> (raw)
In-Reply-To: <20140415112757.GI3271@calimero.vinschen.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
next prev parent reply other threads:[~2014-04-15 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 7:22 Gisela Haschmich
2014-04-15 9:31 ` Corinna Vinschen
2014-04-15 11:16 ` Gisela Haschmich
2014-04-15 11:28 ` Corinna Vinschen
2014-04-15 23:53 ` Peter Rosin [this message]
2014-04-16 7:21 ` Gisela Haschmich
2014-04-16 8:03 ` Corinna Vinschen
2014-04-16 12:07 ` tednolan
2014-04-16 13:59 ` Corinna Vinschen
2014-04-16 9:34 ` Peter Rosin
2014-04-17 8:46 ` szgyg
2014-04-17 9:57 ` Peter Rosin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=534DC67C.3080909@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).