LKML Archive on
help / color / mirror / Atom feed
From: Jeff Garzik <>
To: Andrea Arcangeli <>
Cc: Keith Owens <>,
Subject: Re: [patch] 2.4.11-pre4 remove spurious kernel recompiles
Date: Sun, 7 Oct 2001 13:16:19 -0500 (CDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20011007200522.E726@athlon.random>

On Sun, 7 Oct 2001, Andrea Arcangeli wrote:

> On Sun, Oct 07, 2001 at 08:25:42PM +1000, Keith Owens wrote:
> > in the top level Makefile forces a recompile of the entire kernel, for
> > no good reason.
> this is a matter of taste but personally I believe that at least
> theorically recompiling the whole kernel if I add -g to CFLAGS, or if I
> change the EXTRAVERSION have lots of sense.

Correct.  I am amazed Keith missed this...  changing data in Makefile
can certainly affect the entire kernel compile, so it makes sense to
recompile the entire kernel when it changes.

If we want to change this, one must isolate the specific changes which
cause the entire kernel (or just init/main.c) to be recompiled, and
put those in a separate file.

> OTOH at the moment I
> wouldn't trust the buildsystem anyways, so I'd run a `make distclean`
> anyways in those cases :).

ditto :)  my kbuild script looks basically like:

make distclean && cp <kconfig dir>/rum .config && make oldconfig &&
make oldconfig && make -j3 dep && make -j3 && make modules && make boot


  reply	other threads:[~2001-10-07 18:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 10:25 [patch] 2.4.11-pre4 remove spurious kernel recompiles Keith Owens
2001-10-07 18:05 ` Andrea Arcangeli
2001-10-07 18:16   ` Jeff Garzik [this message]
2001-10-07 23:29     ` Keith Owens
2001-10-08  0:05       ` Andrea Arcangeli
2001-10-08  0:42         ` Keith Owens
2001-10-08  1:20           ` Andrea Arcangeli
2001-10-08  1:34             ` Keith Owens
2001-10-08  2:12               ` Andrea Arcangeli
2001-10-08  2:49                 ` Keith Owens
2001-10-08  3:07                   ` Andrea Arcangeli
2001-10-08 17:56               ` bill davidsen
2001-10-08 16:19 ` 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:

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

  git send-email \ \ \ \ \ \

* 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 NNTP newsgroup(s).