This is the mail archive of the
mailing list for the Cygwin project.
RE: Lot of undefined symbols at link time, even with -l option on good libraries
- From: Larry Hall <lh-no-personal-replies-please at cygwin dot com>
- To: "Dave Korn" <dk at artimi dot com>, "'Cygwin List'" <cygwin at cygwin dot com>
- Date: Wed, 22 Sep 2004 13:36:44 -0400
- Subject: RE: Lot of undefined symbols at link time, even with -l option on good libraries
- References: <4151B11A.firstname.lastname@example.org> <NUTMEGFCHOzyfyz5b6K00000028@NUTMEG.CAM.ARTIMI.COM>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
At 01:14 PM 9/22/2004, you wrote:
>> -----Original Message-----
>> From: Frédéric ORMANCEY
>> Sent: 22 September 2004 18:07
>> I did it, but it don't work !
> Ah, ok, that was not clear from your last message!
>> The --enable-stdcall-fixup option suppress one warning on top
>> of linker output trace :
>> AVERTISSEMENT: résolution de _GetModuleHandleA par un
>> lien vers _GetModuleHandleA@4
>> and unfortunatly leave ALL other errors with no effect on it.
> I see. Hmm. That's very strange; it should affect all the errors - that
>is, if they're all the same kind of error. OTOH it could be that you've
>gotten the calling conventions wrong with the other pragmas, so that's why
>--enable-stdcall-fixup doesn't work for them; there must be some different
>reason why the errors are caused, since they behave differently.
> You might care to experiment with the "--enable-auto-import" and, failing
>that, "--enable-extra-pe-debug" options as well.
Or Frédéric could try specifying the link symbol he wants in the pragma
as suggested by an earlier poster (sorry, the thread is broken in the
archives and I didn't put any effort into wading through the messages
to trace it all back to that message).
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html