This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: libtool: link: object name conflicts in archive
- From: tednolan at bellsouth dot net
- To: cygwin at cygwin dot com
- Date: Wed, 16 Apr 2014 07:35:04 -0400
- Subject: Re: libtool: link: object name conflicts in archive
- Authentication-results: sourceware.org; auth=none
- References: <7c71eb34219779df3fb3d492f29bcead at mail dot eclipso dot de> <20140415093113 dot GF3271 at calimero dot vinschen dot de> <22601c400b5e0fffb54b32a9d6b2bdf8 at mail dot eclipso dot de> <20140415112757 dot GI3271 at calimero dot vinschen dot de> <534DC67C dot 3080909 at lysator dot liu dot se> <d9e573a45fdb88940ab5064aa333cccb at mail dot eclipso dot de> <20140416080331 dot GN3271 at calimero dot vinschen dot de>
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.
--
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