Re: libtool: link: object name conflicts in archive

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

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=utf-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
> >
> 
> 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..
> 
> 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

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

Attachment: pgpaMBE7EihbG.pgp
Description: PGP signature