From: Sam Ravnborg <sam@ravnborg.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kai@germaschewski.name
Subject: Re: 2.6.11-bk10 build problems
Date: Mon, 14 Mar 2005 22:22:34 +0100 [thread overview]
Message-ID: <20050314212234.GC17925@mars.ravnborg.org> (raw)
In-Reply-To: <566920000.1110832470@flay>
>
> > 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 =====
--- 1.80/arch/i386/Makefile 2005-03-12 08:48:59 +01:00
+++ edited/arch/i386/Makefile 2005-03-14 22:20:56 +01:00
@@ -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
next prev parent reply other threads:[~2005-03-14 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 19:39 Dave Hansen
2005-03-14 19:49 ` Sam Ravnborg
2005-03-14 19:57 ` Dave Hansen
2005-03-14 20:34 ` Martin J. Bligh
2005-03-14 21:22 ` Sam Ravnborg [this message]
2005-03-14 21:31 Martin J. Bligh
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=20050314212234.GC17925@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®