From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
jsimmons@infradead.org, "Justin T. Gibbs" <gibbs@scsiguy.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6: spurious recompiles
Date: Sun, 7 Sep 2003 07:33:09 +0200 [thread overview]
Message-ID: <20030907053309.GA963@mars.ravnborg.org> (raw)
In-Reply-To: <20030906201417.GI14436@fs.tum.de>
On Sat, Sep 06, 2003 at 10:14:18PM +0200, Adrian Bunk wrote:
> 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
configs.o included compile.h. Compile.h contains date when kernel was
compiled, and gets updated each time there is new .o files.
That is fixed in patch sent to Randy.
> 2. pnmtologo
> The following happens again once, but not when doing a third "make":
> ./scripts/pnmtologo -t mono -n logo_linux_mono -o drivers/video/logo/logo_linux_mono.c drivers/video/logo/logo_linux_mono.pbm
> CC drivers/video/logo/logo_linux_mono.o
> ./scripts/pnmtologo -t vga16 -n logo_linux_vga16 -o drivers/video/logo/logo_linux_vga16.c drivers/video/logo/logo_linux_vga16.ppm
> CC drivers/video/logo/logo_linux_vga16.o
> ./scripts/pnmtologo -t clut224 -n logo_linux_clut224 -o drivers/video/logo/logo_linux_clut224.c drivers/video/logo/logo_linux_clut224.ppm
> CC drivers/video/logo/logo_linux_clut224.o
> LD drivers/video/logo/built-in.o
> LD drivers/video/built-in.o
I have sent a patch to James Simmons some time ago. I will try to dig it
up and see if it still applies, and fixes the problem.
> 3. aic7xxx
> drivers/scsi/aic7xxx/aicasm/aicasm -Idrivers/scsi/aic7xxx -r
> drivers/scsi/aic7xxx/aic79xx_reg.h \
> -p drivers/scsi/aic7xxx/aic79xx_reg_print.c -i
> aic79xx_osm.h -o drivers/scsi/aic7xxx/aic79xx_seq.h \
> drivers/scsi/aic7xxx/aic79xx.seq
> drivers/scsi/aic7xxx/aicasm/aicasm: 785 instructions used
> CC drivers/scsi/aic7xxx/aic79xx_core.o
New to me, I will take a look.
Sam
next prev parent reply other threads:[~2003-09-07 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 20:14 2.6: spurious recompiles Adrian Bunk
2003-09-06 22:33 ` Randy.Dunlap
2003-09-07 10:37 ` Adrian Bunk
2003-09-07 5:33 ` Sam Ravnborg [this message]
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
[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
2003-09-07 5:36 ` Sam Ravnborg
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=20030907053309.GA963@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@fs.tum.de \
--cc=gibbs@scsiguy.com \
--cc=jsimmons@infradead.org \
--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.