Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <C322F78942E6D311AF8800D0B73C4FD8830DD1@CUPEX3.rational.com>
From: "Masterson, Dave" <dmasters AT rational DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: long double support in cygwin
Date: Sun, 12 Nov 2000 15:13:26 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

I believe the distinction between GPL and LGPL is in the derivation from
something licensed under each -- not in the distribution of something
licensed under each.  I look at it this way:

I link my program with a library that has been LGPL'ed -- what do I do?

* You must make available the source code to the *LIBRARY*.
* You may distribute the source code to your program if you choose.

I link my program with a library that has been GPL'ed -- what do I do?

* You must make available the source code to the *LIBRARY*.
* Due to derivation, you must make your program's source available as well.


-----Original Message-----
From: Christopher Faylor [mailto:cgf AT redhat DOT com]
Sent: Sunday, November 12, 2000 3:00 PM
To: cygwin AT cygwin DOT com
Subject: Re: long double support in cygwin


>>The LGPL still requires that source code be distributed if you are
>>*providing the library* does it not?  If I try to sell you a copy of
>>glibc, I will have to provide you with the sources.  If I sell you a
>>copy of a program linked with glibc, I don't have to give you the
>>sources for glibc.  It's a subtle distinction, but this is why we can't
>>use it.
>
>Not quite.  If you built a problem with glibc (or cygwin, under the
>LGPL), you are *always* required to distribute the sources for the
>LGPL'd components, and whatever else it takes to rebuild the
>application at least from those sources (normally, this means a .o for
>your app).  The LGPL *still* requires that the user be able to change
>the LGPL'd components and rebuild the app.  It just doesn't require
>that you be able to rebuild the app from *its* sources.

If your application uses a LGPL'ed shared library, as is the case with
glibc, you don't need to include sources.  Or, at least that is my
understanding of section 6b of the LGPL.  If you have linked in
components of the library into your application (i.e., cygwin) then you
do.

That is what I was alluding to.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com