From: Boaz Harrosh <bharrosh@panasas.com>
To: Sam Ravnborg <sam@ravnborg.org>, Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] Use relative symbolic links for bzImge in x86 ARCHs
Date: Thu, 18 Oct 2007 17:30:48 +0200 [thread overview]
Message-ID: <47177C28.5010609@panasas.com> (raw)
In-Reply-To: <20071017191633.GB11837@uranus.ravnborg.org>
OK One more problem with a patch this time
---
From: Benny Halevy <bhalevy@panasas.com>
use relative paths in the symlink to bzImage
to make it NFS export safe.
Signed-off-by: Benny Halevy <bhalevy@panasas.com>
diff --git a/arch/i386/Makefile b/arch/i386/Makefile
index f036d2d..396146e 100644
--- a/arch/i386/Makefile
+++ b/arch/i386/Makefile
@@ -132,7 +132,7 @@ zImage zlilo zdisk: KBUILD_IMAGE := arch/x86/boot/zImage
zImage bzImage: vmlinux
$(Q)mkdir -p $(objtree)/arch/i386/boot
- $(Q)ln -fsn $(objtree)/arch/x86/boot/bzImage $(objtree)/arch/i386/boot/bzImage
+ $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/i386/boot/bzImage
$(Q)$(MAKE) $(build)=$(boot) $(KBUILD_IMAGE)
compressed: zImage
diff --git a/arch/x86_64/Makefile b/arch/x86_64/Makefile
index 9daa32d..8048f4f 100644
--- a/arch/x86_64/Makefile
+++ b/arch/x86_64/Makefile
@@ -98,7 +98,7 @@ KBUILD_IMAGE := $(BOOTIMAGE)
bzImage: vmlinux
$(Q)mkdir -p $(objtree)/arch/x86_64/boot
- $(Q)ln -fsn $(objtree)/arch/x86/boot/bzImage $(objtree)/arch/x86_64/boot/bzImage
+ $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/x86_64/boot/bzImage
$(Q)$(MAKE) $(build)=$(boot) $(BOOTIMAGE)
bzlilo: vmlinux
next prev parent reply other threads:[~2007-10-18 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 11:32 slight annoyance with new x86 arch Boaz Harrosh
2007-10-17 19:16 ` [PATCH] x86: fix kernel rebuild due to vsyscall fallout Sam Ravnborg
2007-10-17 19:26 ` Thomas Gleixner
2007-10-18 15:30 ` Boaz Harrosh [this message]
2007-10-18 15:54 ` [PATCH] Use relative symbolic links for bzImge in x86 ARCHs Sam Ravnborg
2007-10-18 16:00 ` Boaz Harrosh
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=47177C28.5010609@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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.