Date: Sun, 28 Apr 1996 11:47:46 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: stiletto AT psu DOT edu
Cc: djgpp AT delorie DOT com, Ryan Drake <drake AT psu DOT edu>
Subject: Re: GNU question.
In-Reply-To: <4lrf0m$11ct@hearst.cac.psu.edu>
Message-Id: <Pine.SUN.3.91.960428114336.29143B-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 26 Apr 1996, Ryan Drake wrote:

> What I don't understand is what the difference between DJGPP's
> libc.a and GNU's libgcc.a as far as what functions each contains.

libgcc.a is nothing to be concerned about license-wise.  Only libgpp.a 
imposes LGPL on the applications.  Therefore, if you work in C, you have 
nothing to worry about as long as your source (not the libraries) doesn't 
include something that was lifted from some GNU program.  If you work in 
C++, try linking without -lgpp at first: many classes are in libiostream 
and libstdcxx which aren't GPL/LGPL; only if you still have unresolved 
externals, append -lgpp.