From: Giacomo Catenazzi <cate@math.ethz.ch>
To: Keith Owens <kaos@ocs.com.au>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Announce: Kernel Build for 2.5, Release 1 is available.
Date: Wed, 08 Aug 2001 13:33:38 +0200 [thread overview]
Message-ID: <3B712392.A7CFEEC9@math.ethz.ch> (raw)
In-Reply-To: <31408.997253881@kao2.melbourne.sgi.com>
Keith Owens wrote:
>
> Supports a common source and object directory. The default mode is
> the same as kbuild 2.4, to use the same tree for both source and
> object. Even in this mode, kbuild 2.5 treats almost all the source
> files as read only, no more time stamp fiddling with .h files. The
> exceptions are files that are generated at run time and are
> incorrectly being shipped as part of the kernel tar ball. I will be
> sending patches to remove these files from the 2.4 tar ball.
> Obviously you can only compile one kernel at a time in this mode.
Warning:
If generating some support files requires some non common tools,
it is the right thing to ship the two files (source and generated).
(also GNU std requires it (IIRC compiling a package
should not require m4, autoconfig, automake, and some tex preprocessing
for info files).
I agree with GNU, thus compiling kernel should not require
some non-common tools (python, gawk are 'common' tools for me).
BTW we cannot ship the generated file without the source files,
because of GPL.
giacomo
next prev parent reply other threads:[~2001-08-08 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 6:58 Announce: Kernel Build for 2.5, Release 1 is available Keith Owens
2001-08-08 7:38 ` john slee
2001-08-08 11:07 ` Keith Owens
2001-08-08 11:33 ` Giacomo Catenazzi [this message]
2001-08-08 11:39 ` [kbuild-devel] " Christoph Hellwig
2001-08-08 11:48 ` Giacomo Catenazzi
2001-08-08 11:54 ` Christoph Hellwig
2001-08-08 12:06 ` Giacomo Catenazzi
2001-08-08 12:00 ` Andy Walker
2001-08-08 11:50 ` Keith Owens
2001-08-08 11:56 ` Alan Cox
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=3B712392.A7CFEEC9@math.ethz.ch \
--to=cate@math.ethz.ch \
--cc=cate@dplanet.ch \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.