2.6: spurious recompiles
Quoted 12 lines · Randy.Dunlap
Quoted 7 lines
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
CCkernel/configs.o
even when the .config wasn't changedThis is probably the same thing that Steve Hemminger posted about yesterday:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106270067411137&w=2
Quoted 5 lines
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=2or 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
Quoted 9 lines · Andi Kleen
"Randy.Dunlap" <[email protected]> writes:
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.Sis an assembly file which depends onasm/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 thevsyscall.Sfile.
Hi Andi, I recall I have a mail from you about this.
Last time I looked I could not figure out what was wrong, but let me try again.
Could you send me the output of "make V=1" for an otherwise clean compile.
Sam