DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=rcYg
	ZHw3YQnFtCAbav5MC3Jqfg715U15gy/uhLs/HwyhaQFWV334jRrauXc5T9KOZp7k
	WKjQqSt9wSBKAo11Y12uMk+c1sI7RCiI1AL8DF/LxHo+3P3vqND5TCexh6s3qX2/
	T8GD0DTN/XE4RgBGXmWWZhSL/49axC9/pSsyWXw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 15 Apr 2014 13:27:57 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Re: libtool: link: object name conflicts in archive
Message-ID: <20140415112757.GI3271@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <7c71eb34219779df3fb3d492f29bcead@mail.eclipso.de> <20140415093113.GF3271@calimero.vinschen.de> <22601c400b5e0fffb54b32a9d6b2bdf8@mail.eclipso.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="/LSm8UPTCLHL4o89"
Content-Disposition: inline
In-Reply-To: <22601c400b5e0fffb54b32a9d6b2bdf8@mail.eclipso.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

--/LSm8UPTCLHL4o89
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
> > >
>=20
> > > libtool: link: object name conflicts in archive: .libs/libmbwrap.lax/=
liby12.lib//home/ntmoe/mbdyn-1.5.5/libraries/liby12/.libs/liby12.lib
>=20
> > >
> > > i found with google, that it could be an error with path variable, be=
cause
> > 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 s=
hould use instead ?

gcc uses ld from binutils.  There's really no reason to have any VC tool
in the path.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--/LSm8UPTCLHL4o89
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTTRe9AAoJEPU2Bp2uRE+gTr0QAJ0k4+d7MwdDxHtdJcD2E3Hf
y6Dc96kDFrFcCxO4vcMRWH/LH+sk5C1gyToj24wSaTzgur/QNlRThhrfi3tfzUFc
me8uWOLToqEWfxYH/W/JgQzyCljvWWsA8N2fzgm5lb5hq1P/6lRyr82ah8nBA9xb
a44+f+Rx/S/o+NFv4QcmE9EBztopiC64Fix9tskcXOEnHZnVEQdA0nl0YLZeEj+c
O10dvSU/pB3sPnpSoNj+smu/X5Dio1B5qLfuoG4Y40tRv6zN1tis9BwEb6lRa1AN
QxYngO8FIky4S/ckOS72jY5QywQlkjonB+BCUAO6qSa21KfndD667y0PGdqPOwo0
aB03sYI5c4p2mDEwvOPhryiINTzeBHoGsb7Q0VFwMdCVkfORUjBK6cvqCfq9PbKG
mYt2PT4RdV5OIwr1v9xv2j5Eau91vaQIaGAnUOJxXiESNEQMOwK+CJ+QmI3Bq30/
gS+XWRzXYI9yuGlyU2UyZVDS5HJr9rk2Lctul0x2V6Gfm3qzl/Xfc7Dz3zDJNR2/
QGicqjgL7j7wTP3ENhz0JqGtCeO07qwHCu6yAQ3hlF/G/R7Tv0UXdVOYxRBJsEU8
w5pPQK3ni8GYvosMq01kNNkUCfUFM+kUoMHHsvrF0OX8euILY4b1srYQ+I7nHNpP
PnMMBVXVApbn+AJz4wBg
=J4Nc
-----END PGP SIGNATURE-----

--/LSm8UPTCLHL4o89--