From: fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject: libc.a vs libgcc.a (was: Hip, Hip, Hooray for b19)
1 Mar 1998 23:48:32 -0800
Message-ID: <19980302171359.18282.cygnus.gnu-win32@murlibobo.cs.mu.OZ.AU>
References: <199803011559 DOT HAA29481 AT proxyb2 DOT san DOT rr DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: mlx AT san DOT rr DOT com
Cc: gnu-win32 AT cygnus DOT com

On 01-Mar-1998, Steve Biskis <mlx AT san DOT rr DOT 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 AT cs DOT mu DOT oz DOT 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 AT 128 DOT 250 DOT 37 DOT 3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".