Date: Thu, 18 Dec 1997 17:18:59 -0800 (PST)
Message-Id: <199712190118.RAA12032@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: ANNOUNCE - GCC 2.7.2.1 Patched available for download
Cc: crough45 AT amc DOT de, salvador AT inti DOT gov DOT ar, djgpp AT delorie DOT com
Precedence: bulk

At 01:06  12/18/1997 +0200, Eli Zaretskii wrote:
>
>On Wed, 17 Dec 1997, Christopher Croughton wrote:
>
>> (Your $0.02 makes more /c/e/n/t/s/ sense than most of us, which was why
>> I posed the question.  I've been reading the (L)GPL and gotten totally 
>> confused, resulting in deciding not to use it for my software...)
>
>Another $0.02:
>
>Actually, even DJGPP is only free as long as you don't change it.  If
>you change some of the DJGPP sources (like some libc functions), the
>changed version immediately falls under GPL/LGPL.
Another question: Suppose I wanted to use some of DJGPP's source code in my
program. (For instance, take the libc printf and adapt it to my own needs,
or borrow some code from djtar.) Of course I would credit the source (no pun
intended) but would I also have to distribute my program under GPL? I know
that GNU programs work this way (you can borrow GCC code, but you then fall
under GPL), but what about DJGPP-specific code?

Nate Eldredge
eldredge AT ap DOT net