public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Peter Rosin <peda@lysator.liu.se>
To: cygwin@cygwin.com
Subject: Re: libtool: link: object name conflicts in archive
Date: Wed, 16 Apr 2014 09:34:00 -0000	[thread overview]
Message-ID: <534E4E81.609@lysator.liu.se> (raw)
In-Reply-To: <d9e573a45fdb88940ab5064aa333cccb@mail.eclipso.de>

On 2014-04-16 09:21, Gisela Haschmich wrote:
> 
>> 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).
> 
> 
> I tried it now with
> 
> $ echo $PATH
> /usr/local/bin:/usr/bin:/usr/lib/lapack
> 
> and got lib: command not found
> 
> /bin/sh ../../libtool --tag=F77   --mode=link gfortran     -o liby12.la  y12mae.lo y12maf.lo y12mbe.lo y12mbf.lo y12mce.lo y12mcf.lo y12mde.lo y12mdf.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/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -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 -luser32 -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 -ladvapi32
> -lshell32 -luser32 -lkernel32 -lltdl
> libtool: link: lib -OUT:.libs/liby12.lib .libs/y12mae.o .libs/y12maf.o .libs/y12mbe.o .libs/y12mbf.o .libs/y12mce.o .libs/y12mcf.o .libs/y12mde.o .libs/y12mdf.o .libs/y12mfe.o .libs/y12mge.o .libs/y12mhe.o
> ../../libtool: line 1117: lib: command not found

Did you really rerun configure with the new $PATH? You also need to kill
any configure cache, i.e. if you have one.

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

  parent reply	other threads:[~2014-04-16  9:34 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
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 [this message]
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=534E4E81.609@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).