This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libtool 20030216: problem recognizing import libraries

Teun Burgers wrote:
When I libtoolize with libtool-devel-20030216, I can't build dll's that I was able to
build with libtool-devel-20030103. When linking with 20030216 I get messages such
as these:
I get this message for the following libs:

-lcygwin -luser32 -ladvapi32 -lkernel32 -lshell32

20030103 *does* recognize all these libraries as import-libs/shared libs.
How can I build this shared library with 20030216?

btw unpatched 20030216 can also build this dll.

Not surprising...since the unpatched version uses the old "safe" code.

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


Attachment: cygwin_libid
Description: application/java-applet

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]