From: Sam Ravnborg <sam@ravnborg.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix 32bit build for git-x86
Date: Tue, 15 Jan 2008 08:45:11 +0100 [thread overview]
Message-ID: <20080115074511.GA15285@uranus.ravnborg.org> (raw)
In-Reply-To: <20080115010449.GA5521@basil.nowhere.org>
On Tue, Jan 15, 2008 at 02:04:49AM +0100, Andi Kleen wrote:
>
> Fixes the 32build here with git-x86 (tip 2f42671697ea9abc7d10ea7f663d6ef6e8ec6358)
>
> Fix git-x86 build
>
> Otherwise
>
> make[3]: Nothing to be done for `vmlinux'.
> KBUILD_IMAGE := arch/x86/boot/bzImage
> make[2]: KBUILD_IMAGE: Command not found
> make[2]: *** [all] Error 127
Thanks Andi.
I wonder how these tabs came in.
I am almost sure they were not in my original patch. But as git-send-email
do not save copies of my sent mails I cannot be sure.
Ingo - do you have a script on your side that could have converted
the spaces to tabs?
It could be a simple "make checkpatch happy" change too - but in this case
it was wrong.
Leading tabs in Makefiles that are not in front of commands are a typical
source of non-so-easy-to-debug problems.
Been there before....
Sam
>
> Signed-off-by: Andi Kleen <ak@suse.de>
>
> Index: linux/arch/x86/Makefile
> ===================================================================
> --- linux.orig/arch/x86/Makefile
> +++ linux/arch/x86/Makefile
> @@ -211,7 +211,8 @@ PHONY += zImage bzImage compressed zlilo
> all: bzImage
>
> # KBUILD_IMAGE specify target image being built
> - KBUILD_IMAGE := $(boot)/bzImage
> +KBUILD_IMAGE := $(boot)/bzImage
> +
> zImage zlilo zdisk: KBUILD_IMAGE := arch/x86/boot/zImage
>
> zImage bzImage: vmlinux
next prev parent reply other threads:[~2008-01-15 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 1:04 Andi Kleen
2008-01-15 7:45 ` Sam Ravnborg [this message]
2008-01-15 7:56 ` Junio C Hamano
2008-01-15 8:53 ` Ingo Molnar
2008-01-15 9:00 ` Ingo Molnar
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=20080115074511.GA15285@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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®