From: Thomas Gleixner <tglx@linutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: fix kernel rebuild due to vsyscall fallout
Date: Wed, 17 Oct 2007 21:26:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0710172126110.24155@localhost.localdomain> (raw)
In-Reply-To: <20071017191633.GB11837@uranus.ravnborg.org>
On Wed, 17 Oct 2007, Sam Ravnborg wrote:
> Fix rebuild of kernel when there is no changes.
> This happened for i386.
> Using make V=2 hinted that the output files were
> not assigned to targets - fixed by this patch.
>
> Reported by: Boaz Harrosh <bharrosh@panasas.com>
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> ---
> diff --git a/arch/x86/kernel/Makefile_32 b/arch/x86/kernel/Makefile_32
> index 7ff0206..a3fa11f 100644
> --- a/arch/x86/kernel/Makefile_32
> +++ b/arch/x86/kernel/Makefile_32
> @@ -51,7 +51,7 @@ obj-$(CONFIG_SCx200) += scx200_32.o
> # We must build both images before we can assemble it.
> # Note: kbuild does not track this dependency due to usage of .incbin
> $(obj)/vsyscall_32.o: $(obj)/vsyscall-int80_32.so $(obj)/vsyscall-sysenter_32.so
> -targets += $(foreach F,int80 sysenter,vsyscall-$F.o vsyscall-$F.so)
> +targets += $(foreach F,int80 sysenter,vsyscall-$F_32.o vsyscall-$F_32.so)
> targets += vsyscall-note_32.o vsyscall_32.lds
>
> # The DSO images are built using a special linker script.
Thanks, applied
tglx
next prev parent reply other threads:[~2007-10-17 19:27 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 [this message]
2007-10-18 15:30 ` [PATCH] Use relative symbolic links for bzImge in x86 ARCHs Boaz Harrosh
2007-10-18 15:54 ` 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=alpine.LFD.0.9999.0710172126110.24155@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 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®