lists.zerezo.com
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
***BOGO*** [Mingw-users] Odd link messages. Are they dangerous?
- Date: Fri, 10 Oct 2008 00:56:13 +0800
- From: "Bruce M. Axtens" <bruce.axtens@xxxxxxxxx>
- Subject: ***BOGO*** [Mingw-users] Odd link messages. Are they dangerous?
I used the MinGW .a to Windows .lib transformation process as detailed
in a thread on the gmp-discuss list, as below (acting against a GMP
4.2.4 library created with --disable-shared --enable-static.)
cp libgmp.a gmp.a
ranlib gmp.a
mv gmp.a gmp.lib
I now have a .lib file against which VC++6 seems to have no difficulty
linking. What concerns me now is warning messages I'm getting from the
link phase:
LINK : warning LNK4049: locally defined symbol "___mb_cur_max" imported
LINK : warning LNK4049: locally defined symbol "__pctype" imported
LINK : warning LNK4049: locally defined symbol "__iob" imported
At this point in the proceedings these make no difference to the running
of my DLL (which wraps certain GMP functionality). But is that good
enough? Will having these three symbols from libgmp.a linked in to my
Windows DLL end up biting me later on?
Kind regards,
Bruce.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users