From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-kernel@vger.kernel.org
Subject: Re: GPL license and linux kernel modifications
Date: Tue, 27 Jan 2004 09:33:38 -0700 [thread overview]
Message-ID: <401692E2.7010800@backtobasicsmgmt.com> (raw)
In-Reply-To: <E1AlW2F-000N9k-00.bansh21-mail-ru@f13.mail.ru>
Bansh wrote:
> special exception, the source code distributed need not include
> anything that is normally distributed (in either source or binary
> form) with the major components (compiler, kernel, and so on) of the
> operating system on which the executable runs, unless that component
> itself accompanies the executable.
> ----------- cut COPYING -----------
>
> It gives the possibility to not distribute compiler and other preprocessing tools.
> It looks like one can make a preprocessor or even one's own compiler (with one's syntax) which will be used for kernel building. But it's not required to distribute this compiler. So I can distribute linux kernel source code modified this way but no one will be able to build it. Is it ok?
Only if those "compiler and other preprocessing tools" are normally
distributed with the O/S the executable runs on. If you create your own
compiler, and it's not "normally distributed", then you can't publish
source code in that language under the GPL without making the compiler
available as well.
next prev parent reply other threads:[~2004-01-27 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 16:25 GPL license and linux kernel modifications "Bansh"
2004-01-27 16:33 ` Kevin P. Fleming [this message]
2004-01-27 17:56 ` Måns Rullgård
2004-01-29 2:55 ` Valdis.Kletnieks
2004-01-29 11:14 ` David Schwartz
2004-02-01 20:49 ` Bill Davidsen
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=401692E2.7010800@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.org \
/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