This is the mail archive of the
mailing list for the Cygwin project.
Re: libtool 20030216: problem recognizing import libraries
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Teun Burgers <a dot rburgers at freeler dot nl>
- Cc: cygwin at cygwin dot com
- Date: Fri, 7 Mar 2003 15:09:30 -0500 (EST)
- Subject: Re: libtool 20030216: problem recognizing import libraries
- Reply-to: cygwin at cygwin dot com
On Fri, 7 Mar 2003, Teun Burgers wrote:
> Teun Burgers wrote:
> > Charles Wilson wrote:
> > > Now, about your problem: I'm a bit confused, because I do *not* see that
> > > behavior. Please take the attached script, which contains only the new
> > > win32_libid() code -- the only parted changed by the patched
> > > libtool-20030216 -- and run the following tests:
> > >
> > > ./cygwin_libid /usr/lib/libcygwin.a
> > > ./cygwin_libid /usr/lib/w32api/libuser32.a
> > > ./cygwin_libid /usr/lib/w32api/libadvapi32.a
> > > ./cygwin_libid /usr/lib/w32api/libkernel32.a
> > > ./cygwin_libid /usr/lib/w32api/libshell32.a
> > >
> > > And report back...
> I've found the culprit. I installed the perl LWP module which
> installs a HEAD script that fetches the header of an URL.
> On unix HEAD and head are different but on cygwin having
> both HEAD and head.exe along the path causes a problem...
> After removing the HEAD script cygwin_libid reports x86 archive import
> So maybe cygwin_libid should call /usr/bin/head.exe instead
> of just head?
This is a problem with the LWP module. FYI, I've reported this to the
maintainers back in September last year: <http://cygwin.com/ml/cygwin/2002-09/msg01385.html>
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html