delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/08/01/08:52:51

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: <BA5F9C6AA352D311AD4E009027855BCD07D35171@fl51m01.space.honeywell.com>
From: "Clark, Matthew C (FL51)" <matthew DOT c DOT clark AT honeywell DOT com>
To: cygwin AT cygwin DOT com
Subject: Licensing terms
Date: Wed, 1 Aug 2001 08:52:31 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)

I'm looking for a little clarification about the GPL that covers 
cygwin, specifically the gcc compiler.  I used to be under the 
impression that if I modified something covered by the GPL (such as 
a linux module, or a cygwin tool), then I'd have to make the changes 
public.  Now it seems that even if I just use/link a GPL'ed object, 
such as libcygwin.a, I have to make any and all source code I might 
have compiled under cygwin's gcc open source.  Is this correct?  
If so, is this specific to cygwin or GPL in general and when 
did this happen?  

Please include me directly in any followup as I only get the digest
version of the cygwin mailing list.  Thanks.

Matt Clark
matthew DOT c DOT clark AT honeywell DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019