public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: earnie_boyd@yahoo.com
Cc: cygwin users <cygwin@sourceware.cygnus.com>
Subject: Re: Does GPL apply without Cygwin stub?
Date: Mon, 08 Mar 1999 11:19:00 -0000	[thread overview]
Message-ID: <19990309061930.63879@mundook.cs.mu.OZ.AU> (raw)
In-Reply-To: < 19990308163406.22270.rocketmail@send101.yahoomail.com >; from Earnie Boyd on Mon, Mar 08, 1999 at 08:34:06AM -0800

On 08-Mar-1999, Earnie Boyd <earnie_boyd@yahoo.com> wrote:
> ---Chris Faylor <cgf@cygnus.com> wrote:
> 8<
> > If they are just distributing the crt0.o module and cygwin1.dll then
> they
> > must make source code available for both.
> 8<
> 
> So does this mean that if I supply my own crt0.o module that my source
> code doesn't have to be made available?

You'd also have to supply your own libcygwin.a.

I believe that at least one release of the GNU Ada compiler gnat
for Windows did exactly that.  This was back around version b17,
when Cygnus had just changed the license.  ACT took the sources
for libcygwin.a from b16, which I think were public domain, and
modified them a bit to make them work with the DLL from b17.

If you do something like that, then it's probably legal.
However, this is a rather gray area; it is not _entirely_ clear
that this would be legal.

P.S.
I am not a lawyer; this is discussion, not legal advice;
if you need legal advice, you should consult an attourney;
#include <std.legal.disclaimer>
yadda yadda yadda...

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >  |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3        |     -- the last words of T. S. Garp.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: earnie_boyd@yahoo.com
Cc: cygwin users <cygwin@sourceware.cygnus.com>
Subject: Re: Does GPL apply without Cygwin stub?
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <19990309061930.63879@mundook.cs.mu.OZ.AU> (raw)
Message-ID: <19990331194500._-DnW9yXHK6GOSZsDlX7OpBAnOT3ZEUptRUBK6BFG3U@z> (raw)
In-Reply-To: <19990308163406.22270.rocketmail@send101.yahoomail.com>

On 08-Mar-1999, Earnie Boyd <earnie_boyd@yahoo.com> wrote:
> ---Chris Faylor <cgf@cygnus.com> wrote:
> 8<
> > If they are just distributing the crt0.o module and cygwin1.dll then
> they
> > must make source code available for both.
> 8<
> 
> So does this mean that if I supply my own crt0.o module that my source
> code doesn't have to be made available?

You'd also have to supply your own libcygwin.a.

I believe that at least one release of the GNU Ada compiler gnat
for Windows did exactly that.  This was back around version b17,
when Cygnus had just changed the license.  ACT took the sources
for libcygwin.a from b16, which I think were public domain, and
modified them a bit to make them work with the DLL from b17.

If you do something like that, then it's probably legal.
However, this is a rather gray area; it is not _entirely_ clear
that this would be legal.

P.S.
I am not a lawyer; this is discussion, not legal advice;
if you need legal advice, you should consult an attourney;
#include <std.legal.disclaimer>
yadda yadda yadda...

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >  |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3        |     -- the last words of T. S. Garp.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  parent reply	other threads:[~1999-03-08 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-08  8:35 Earnie Boyd
     [not found] ` < 19990308163406.22270.rocketmail@send101.yahoomail.com >
1999-03-08 11:19   ` Fergus Henderson [this message]
1999-03-31 19:45     ` Fergus Henderson
1999-03-31 19:45 ` Earnie Boyd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990309061930.63879@mundook.cs.mu.OZ.AU \
    --to=fjh@cs.mu.oz.au \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=earnie_boyd@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).