Skip to contentSkip to conversation

2.6.11-bk10 build problems

DISCUSSION Dave Hansen 3 participants 5 messages Mar 14, 2005

lore
Share & tools
lore
#0 lore raw

I'm having some intermittent build problems on 2.6.11-bk10. First of all, doing a 'make -j8 O=... install' errors out not being able to find a vmlinux:

$ make O=../mhp-build/i386-plain/ -j8 install
make[3]: *** No rule to make target `vmlinux', needed by
`arch/i386/boot/compressed/vmlinux.bin'.  Stop.
make[2]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make[1]: *** [install] Error 2
make: *** [install] Error 2

Also, I just ran menuconfig, changed an option, and did another 'make install', and it went straight to the install script with no compiling.

Note that these are with O=, so it might be just a separate build tree problem.

Any ideas?

-- Dave

#1 lore raw
Quoted 11 lines · Dave Hansen

I'm having some intermittent build problems on 2.6.11-bk10. First of all, doing a 'make -j8 O=... install' errors out not being able to find a vmlinux:

$ make O=../mhp-build/i386-plain/ -j8 install
make[3]: *** No rule to make target `vmlinux', needed by
`arch/i386/boot/compressed/vmlinux.bin'.  Stop.
make[2]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make[1]: *** [install] Error 2
make: *** [install] Error 2
Quoted 8 lines

Also, I just ran menuconfig, changed an option, and did another 'make install', and it went straight to the install script with no compiling.

Note that these are with O=, so it might be just a separate build tree problem.

Any ideas?

On popular request 'make install' no longer try to update vmlinux. This is to avoid errornous recompilation when installing the kernel as root especially when fetching kernel via nfs where path may have changed.

Sam

#2 lore raw
Quoted 4 lines · Sam Ravnborg

On popular request 'make install' no longer try to update vmlinux. This is to avoid errornous recompilation when installing the kernel as root especially when fetching kernel via nfs where path may have changed.

That makes sense, but it's still quite a surprise, and a serious change in behavior from as long as I've been compiling kernels.

How about a new "make install-norebuild" or something that doesn't change current, relied-upon behavior? Seems like the weirdos^Wusers doing kernel fetches over nfs are probably the minority, and their small numbers can be much more easily educated than the masses who expect 'make menuconfig; make install' to do what it's always done.

If that's too invasive, how about restoring the old behavior with a warning to stderr for a release or two?

-- Dave

#3 lore raw
In reply to Sam Ravnborg
Quoted 19 lines · --On Monday, March 14, 2005 20:49:30 +0100 Sam Ravnborg <[email protected]>…
Quoted 18 lines · Dave Hansen

I'm having some intermittent build problems on 2.6.11-bk10. First of all, doing a 'make -j8 O=... install' errors out not being able to find a vmlinux:

$ make O=../mhp-build/i386-plain/ -j8 install
make[3]: *** No rule to make target `vmlinux', needed by
`arch/i386/boot/compressed/vmlinux.bin'.  Stop.
make[2]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make[1]: *** [install] Error 2
make: *** [install] Error 2

Also, I just ran menuconfig, changed an option, and did another 'make install', and it went straight to the install script with no compiling.

Note that these are with O=, so it might be just a separate build tree problem.

Quoted 6 lines
Quoted 1 line

Any ideas?

On popular request 'make install' no longer try to update vmlinux. This is to avoid errornous recompilation when installing the kernel as root especially when fetching kernel via nfs where path may have changed.

That's frigging annoying. It's worked that way for ages, and all our scripts assume it works.

Andrew, can we back that out?

M.

#4 lore raw
Quoted 8 lines
Quoted 5 lines

On popular request 'make install' no longer try to update vmlinux. This is to avoid errornous recompilation when installing the kernel as root especially when fetching kernel via nfs where path may have changed.

That's frigging annoying. It's worked that way for ages, and all our scripts assume it works.

The reason to put it in -mm is to check how things are used. I will change it back and add an:
make kernel_install

kernel_install is then analogous to modules_install

Sam

===== arch/i386/Makefile 1.80 vs edited =====

arch/i386/Makefile +4 -3
@@ -123,7 +123,7 @@
 boot := arch/i386/boot
 
 .PHONY: zImage bzImage compressed zlilo bzlilo \
-	zdisk bzdisk fdimage fdimage144 fdimage288 install
+	zdisk bzdisk fdimage fdimage144 fdimage288 install kernel_install
 
 all: bzImage
 
@@ -145,8 +145,9 @@
 fdimage fdimage144 fdimage288: vmlinux
 	$(Q)$(MAKE) $(build)=$(boot) BOOTIMAGE=$(KBUILD_IMAGE) $@
 
-install:
-	$(Q)$(MAKE) $(build)=$(boot) BOOTIMAGE=$(KBUILD_IMAGE) $@
+install: vmlinux
+install kernel_install:
+	$(Q)$(MAKE) $(build)=$(boot) BOOTIMAGE=$(KBUILD_IMAGE) install
 
 prepare: include/asm-$(ARCH)/asm_offsets.h
 CLEAN_FILES += include/asm-$(ARCH)/asm_offsets.h