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:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=k8N9+pv5K8tHezFbhpDVyID/TA1D6hyUgmfm7X+KYZwYJ9Iue7plS
	3j63zgwlZbNutdfZ5vFF6DdgV4zKToc/k9JEl+4OUJ2kGY3Dha0vZnJrtYAlwQ1V
	TZXmzU+DLP0c09RNKteVxIg3PAfCsA52wridGMM90yOi73Q7mNvYjM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 16 Apr 2014 15:59:24 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: libtool: link: object name conflicts in archive
Message-ID: <20140416135924.GR3271@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <7c71eb34219779df3fb3d492f29bcead@mail.eclipso.de> <20140415093113.GF3271@calimero.vinschen.de> <22601c400b5e0fffb54b32a9d6b2bdf8@mail.eclipso.de> <20140415112757.GI3271@calimero.vinschen.de> <534DC67C.3080909@lysator.liu.se> <d9e573a45fdb88940ab5064aa333cccb@mail.eclipso.de> <20140416080331.GN3271@calimero.vinschen.de> <431111.39076.bm@smtp111.sbc.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="4vu0d+lqoSa2/ZEk"
Content-Disposition: inline
In-Reply-To: <431111.39076.bm@smtp111.sbc.mail.ne1.yahoo.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--4vu0d+lqoSa2/ZEk
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 16 07:35, tednolan@bellsouth.net wrote:
> In message <20140416080331.GN3271@calimero.vinschen.de>you write:
> >--KC+fneiph5CALyUl
> >Content-Type: text/plain; charset=3Dutf-8
> >Content-Disposition: inline
> >Content-Transfer-Encoding: quoted-printable
> >> ../../libtool: line 1117: lib: command not found
> >
> >This is *so* wrong.  That's very likely a problem in the configury then,
> >and you should try to find out how configure gets the idea to use a tool
> >called "lib".  How did you run configure?  This might be a result of
> >using wrong arguments.  Also, the upstream devs might have an idea why
> >the build process tries to use MS tools when building for Cygwin.
> >
> >
> >Corinna
> >
>=20
> I have run into a couple of "configure" scripts that when they see you
> are running cygwin think that means they should try to build a native
> Windows version rather than follow the linux-like path to a "native
> Cygwin" version..
>=20
> It's very irritating.

Indeed.  It's not as bad anymore as 10 years ago, but there are still
packages out there who don't understand that Cygwin is not just a
frontend to build native Windows stuff.


Corinna

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

--4vu0d+lqoSa2/ZEk
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJTToy8AAoJEPU2Bp2uRE+g6MkP/0Njo/MD+kjuHd6mCdSbBbo6
83Cd1JqItYuKdHLRqCgba6BUrdqRh5c1hfRZOD2FIFCLsp34Jt1kC7hsjcSaViPM
CiLqGAyaYY+D+X9Z+KnlD+Tp8sE9Pb2w6yyDkodqYtebdSgW0SeY7VHID9d1lVDS
8rt/0vLsR+EnxlCZMu/g17cwAizfzxAsotWEpa46IXxQZmqlCDF2+9MQFaITpTLg
4GYMTCHxNwk7IPO9NPdrec/bHYKN2aahTn1BFz9KuIa0c44PTW9eTmLsGCE4LNCv
cN9xtUwen5YuTxgB1xibhSpWla6UPWse8gY9CsdE9aQ0crsMmx9Z/xuv5Sfb9nOC
fjPkGD8jK1wTBKAi8yXkbNYq1NwhfDgPW61Q2I9cDdLMWfZGM3EegNZJEkpbe7Rb
XY9bcuGCM3bAsxyDtYmgDkz4yI3l1rAxpW/9jXj6iusIPPnU3+nnJ6/6bmpqh+yA
hRH7xhtfxAc22kKFX7xnmNVkkTv7tJWoqbIHaoTt21g/qUg1uLgclSDZIWjmBhwk
nXWAdpTIjKws8dR4R3Zi+4ISVGGA1o/P9IFlO9mocKrFYOkRQtGzNrDQXwrG7YpU
jm8ZYcMJCjGsWm9JSwfSktc+V4CA1ggyFw9Cnt7w4cC6pQfCS1zk0ZLsOXKmzI00
J9RYdSLIJysxzk7GXe31
=/DjP
-----END PGP SIGNATURE-----

--4vu0d+lqoSa2/ZEk--