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=oDZkXEaE1g0lS9l5abGhpUsXk6IRQ/6uEHivJKeZfgUJadEiRD0Ev
	Lunitk8kIl6ZXDyymuGNRrJvGO0RG4nCF4Pja5/Nej7CVLunmJJUy2IYZDwpx/QW
	B3Hqbg7CKaZdyfVMB81/OJxzrN7k5EV6eLQMSXg3+iVmkcNlB+w/lA=
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 10:03:31 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Re: libtool: link: object name conflicts in archive
Message-ID: <20140416080331.GN3271@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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="KC+fneiph5CALyUl"
Content-Disposition: inline
In-Reply-To: <d9e573a45fdb88940ab5064aa333cccb@mail.eclipso.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Apr 16 07:21, Gisela Haschmich wrote:
>=20
> > 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 libmb=
math.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 bro=
ken
> > and the Microsoft tools are on $PATH (but I haven't tested that).
>=20
>=20
> I tried it now with
>=20
> $ echo $PATH
> /usr/local/bin:/usr/bin:/usr/lib/lapack
>=20
> and got lib: command not found
>=20
> /bin/sh ../../libtool --tag=3DF77   --mode=3Dlink gfortran     -o liby12.=
la  y12mae.lo y12maf.lo y12mbe.lo y12mbf.lo y12mce.lo y12mcf.lo y12mde.lo y=
12mdf.lo y12mfe.lo y12mge.lo y12mhe.lo -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.=
2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/us=
r/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lqu=
admath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl  -L/usr=
/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../..=
/../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/=
4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -lus=
er32 -lkernel32 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64=
-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib=
/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -la=
dvapi32
> -lshell32 -luser32 -lkernel32 -lltdl
> libtool: link: lib -OUT:.libs/liby12.lib .libs/y12mae.o .libs/y12maf.o .l=
ibs/y12mbe.o .libs/y12mbf.o .libs/y12mce.o .libs/y12mcf.o .libs/y12mde.o .l=
ibs/y12mdf.o .libs/y12mfe.o .libs/y12mge.o .libs/y12mhe.o
> ../../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
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--KC+fneiph5CALyUl
Content-Type: application/pgp-signature

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

iQIbBAEBAgAGBQJTTjlTAAoJEPU2Bp2uRE+gMEIP90nRR96Pidj6CI4CyMPAl+HF
hdHaB6yj9O2FJ3mjMdnZy0tzv8py3idKGrvr18Xbjv88MXNx5Cb66EHOEdun/Mng
uwBnwwwETTmzDVJAXr7LC5sgy1/CALNMKzsyCJMhOCbp6DPuiSSEtrEZB+W2HZ9w
P1bw4emI4jMdEg7OYHo13KPP36PQKdhmnFXS20CDFOKulFDcIlxGWqb5fQr4l4Fo
dzOWKFgmXQWevFJYgXAkkfQ1er3l1S2++ZYE9aj5K8IkPwgP+BuEDbTTvHpav/np
kqo+xuWYYBZ7oUxeHBdwzLHJOSdQAVkNzdS5ja/MiWUyPec07I8EzIf7XhHgws+8
hlljs9jPT1FxhU+llzQEFWDj/3NiQA0RoIYlTpfdyMYoDWfmXLYCAASrpK1b905M
HNpxD0M0VcEbZ1MmlMkMNVu0+nKexXsJwbTnuB6Pjkr/QcPZDseR+yzPzrlVpB9J
0aoOMPiy77JjhA/nxmo0872S9qFLCk6nKAJQNw6mVhfnkBmQ/yvHySiFivZk337J
ySVkyq6CgzngaiuNPuorYvd7tgXdWevDdDk843rNltpJlxlG4hZf6v8nqyFBhPO1
dgTmwW65kPfNrwDxP7QnlXXoQczuFLmhwm2uQJU0abB5Q+qNHaWtosqMxZZ0p7s0
UpC8cS5pXuR08wZD15M=
=E11K
-----END PGP SIGNATURE-----

--KC+fneiph5CALyUl--