From: Tommy Reynolds <reynolds@redhat.com>
To: "Catalin Marinas" <c_marinas@yahoo.com>
Cc: newby@teco-xaco.com, roy@karlsbakk.net, linux-kernel@vger.kernel.org
Subject: Re: opening a bzImage?
Date: Wed, 6 Feb 2002 11:21:55 -0600 [thread overview]
Message-ID: <20020206112155.1af89d1b.reynolds@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202052237020.2072-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0202051157130.3136-100000@localhost.localdomain> <Pine.LNX.4.44.0202052237020.2072-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
Uttered "Catalin Marinas" <c_marinas@yahoo.com>, spoke thus:
> On Tue, 5 Feb 2002, Daniel A. Newby wrote:
>
> > > Btw.. Does GPL require them to give me the .config file?
> >
> > definition files, plus the scripts used to control compilation and
> > installation of the executable."
> >
> > IMHO, .config is a "script used to control compilation".
>
> I think (though I might be wrong) this is not considered a "script used to
> control compilation" in GPL acception, even if it does this. It is not
> included in the kernel sources, it is generated by other scripts
> (kconfig.tk for example, which is also generated). This is like, for
> example, intermediar .s files generated from .c ones. Nobody would bother
> to include this in the sources.
I can justify the opposite view: ".config" _IS_ a "script used to control
compilation": just look at how it's used. The "Makefile" (that is shipped with
the sources) does an "include .config" to incorporate the contents of ".config"
into the compilation process, so IMHO it easily qualifies. If fact, some
distributions ;-) include the ".config" files as a matter of course.
--
(Any correlation between the carefully considered options expressed herein
to those of my employer is due entirely to the luck of the latter instead
of the intention of the former.-)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- + -- -- -- -- -- -- -- -- -- --
Tommy Reynolds | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone: +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA | FAX: +1.256.837.3839
Senior Software Developer | Mobile: +1.919.641.2923
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2002-02-06 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:42 opening a bzImage? Roy Sigurd Karlsbakk
2002-02-05 14:54 ` Drew P. Vogel
2002-02-05 15:05 ` Roy Sigurd Karlsbakk
2002-02-05 15:07 ` Drew P. Vogel
2002-02-05 15:13 ` Roy Sigurd Karlsbakk
2002-02-05 15:29 ` Drew P. Vogel
2002-02-05 15:40 ` Roy Sigurd Karlsbakk
2002-02-06 9:03 ` Horst von Brand
2002-02-06 14:40 ` Drew P. Vogel
2002-02-06 14:50 ` opening a bzImage? (cancelled?) Roy Sigurd Karlsbakk
2002-02-06 15:02 ` Drew P. Vogel
2002-02-06 15:22 ` Alan Cox
2002-02-06 15:22 ` Rik van Riel
2002-02-06 22:41 ` Florian Schmitt
2002-02-05 15:15 ` opening a bzImage? Chris Funderburg
2002-02-05 17:22 ` Catalin Marinas
2002-02-06 7:40 ` Daniel Phillips
2002-02-05 18:19 ` Daniel A. Newby
2002-02-05 22:55 ` Catalin Marinas
2002-02-06 10:14 ` Horst von Brand
2002-02-06 17:21 ` Tommy Reynolds [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-06 0:25 Telford002
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=20020206112155.1af89d1b.reynolds@redhat.com \
--to=reynolds@redhat.com \
--cc=c_marinas@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=newby@teco-xaco.com \
--cc=roy@karlsbakk.net \
/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