This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
libc.a vs libgcc.a (was: Hip, Hip, Hooray for b19)
- To: mlx at san dot rr dot com
- Subject: libc.a vs libgcc.a (was: Hip, Hip, Hooray for b19)
- From: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Date: Mon, 2 Mar 1998 17:13:59 +1100
- Cc: gnu-win32 at cygnus dot com
- References: <199803011559.HAA29481@proxyb2.san.rr.com>
On 01-Mar-1998, Steve Biskis <mlx@san.rr.com> wrote:
> Whats the difference between libgcc.a & libc.a?
libgcc.a contains a few small routines used by gcc-compiled code
(gcc inserts implicit calls to routines in libgcc.a),
whereas libc.a is the standard C library
(which is called explicitly rather than implicitly).
In b19, libc.a is part of cygwinb19.dll / libcygwin.a,
whereas libgcc.a is not.
> It looks like libc is the one used by the dll since you get
> "_impure_ptr redefined" warnings if you try to put it and -lcygwin
> on a link line together but things still compile. So what are the
> pros and cons of linking one vs. the other ?
If you want to use cygwin*.dll, then you should link with -lgcc and -lcygwin,
not with -lc.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh> | of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3 | -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".