Date:	Tue, 18 May 93 10:26:04 EDT
From:	DJ Delorie <dj AT ctron DOT com>
To:	karna AT pobox DOT upenn DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: A question about FSF license

> From: Animesh Karna <karna AT pobox DOT upenn DOT edu>
> Posted-Date: Tue, 18 May 93 9:24:33 EDT
> Date: Tue, 18 May 93 9:24:33 EDT
> X-Mailer: ELM [version 2.3 PL11-upenn1.12]
> DJ-Mail-Sort: djgpp@, djgpp


> I'm not sure I understand some details regarding the FSF license.  Suppose
> I use a library that is covered by the FSF license: I link this library
> into a program I am writing.  I am under the impression that this means that
> my program then becomes a "derived work", and must also be distributed by
> the FSF license (i.e., it must be free and I must include source code). 

If the library is protected by the LGPL (Library General Public
License), then you must ship object files for your part and sources
for the library, instead of sources for everything.  If the library is
protected by the regular GPL, then you are correct.

> What happens, however, if I use a commercial library (or any library not
> covered by the FSF license) in addition to a library that is covered by the
> FSF license?  Is this a no-no?  I get the impression that the source for
> all libraries must be free and available.  

If the commercial library cannot be shipped as per the terms of the
GPL (source form) or LGPL (object form), then you cannot use that
library and GPL/LGPL code in the same binary and ship it.  Most
libraries cannot be shipped under the terms of the GPL/LGPL.  Note
that you can do whatever you want with binaries used only personally
(i.e. not shipped to anyone).

- Raw text -