All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6: spurious recompiles
Date: 07 Sep 2003 00:44:24 +0200	[thread overview]
Message-ID: <p733cf9lepj.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <33384.4.4.25.4.1062887601.squirrel@www.osdl.org.suse.lists.linux.kernel>

"Randy.Dunlap" <rddunlap@osdl.org> writes:

> > When doing a "make" inside an already compiled kernel source there
> > shouldn't be anything rebuilt. I've identified three places where this
> > isn't the case in recent 2.6 kernels:
> >
> > 1. ikconfig
> >   CC      kernel/configs.o
> > even when the .config wasn't changed
> 
> This is probably the same thing that Steve Hemminger posted about
> yesterday:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106270067411137&w=2
> 
> I posted a patch based on Sam Ravnborg's comments that might fix it,
> but I haven't verified it yet... The patch is in this message:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106272687506379&w=2
> 
> or it may be some other dependency.  I'll look into it.

x86-64 has the same problem. It always rebuilds arch/x86_64/ia32/vsyscall32.so,
no matter if it has changed or not. I have not figured out why it does that.

vsyscall.S is an assembly file which depends on asm/offset.h, which 
is regenerated each build. But the regeneration is written in a way to 
not trigger rebuilds when nothing has changed. That works for everything
else, just apparently not for the vsyscall.S file.

-Andi

       reply	other threads:[~2003-09-06 22:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030906201417.GI14436@fs.tum.de.suse.lists.linux.kernel>
     [not found] ` <33384.4.4.25.4.1062887601.squirrel@www.osdl.org.suse.lists.linux.kernel>
2003-09-06 22:44   ` Andi Kleen [this message]
2003-09-07  5:36     ` 2.6: spurious recompiles Sam Ravnborg
2003-09-06 20:14 Adrian Bunk
2003-09-06 22:33 ` Randy.Dunlap
2003-09-07 10:37   ` Adrian Bunk
2003-09-07  5:33 ` Sam Ravnborg
2003-09-08 23:45   ` James Simmons
2003-09-07  5:51 ` Sam Ravnborg
2003-09-07  7:00   ` Sam Ravnborg
2003-09-07 10:17     ` Adrian Bunk
2003-09-08 23:45     ` James Simmons

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=p733cf9lepj.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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.