public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: cate@dplanet.ch
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 21:50:59 +1000	[thread overview]
Message-ID: <1556.997271459@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 08 Aug 2001 13:33:38 +0200." <3B712392.A7CFEEC9@math.ethz.ch>

On Wed, 08 Aug 2001 13:33:38 +0200, 
Giacomo Catenazzi <cate@math.ethz.ch> wrote:
>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).

Absolutely agree.  But we have files in the tar ball that are generated
using standard tools.

net/802/pseudo/pseudocode.h is shipped, but it is generated using sed.
net/802/pseudo/actionnm.h is shipped, it is generated using sed,
nothing even uses the file.
net/802/transit/pdutr.h and timertr.h are shipped but they are
generated using awk.
net/802/cl2llc.c is shipped but it is generated using sed.

I will remove all of those from the tar ball.

OTOH, files like defkeymap.c (needs loadkeys) or the 53c8xx, 53c7xx and
sim710 firmware (need Perl) must have shipped versions in the tar ball,
I will not be removing them.


  parent reply	other threads:[~2001-08-08 11:51 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 ` [kbuild-devel] " Giacomo Catenazzi
2001-08-08 11:39   ` 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 [this message]
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=1556.997271459@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=cate@dplanet.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox