From: Andi Kleen <andi@firstfloor.org>
To: mingo@elte.hu, sam@ravnborg.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Latest git-x86 doesn't build on 32bit
Date: Mon, 14 Jan 2008 23:16:08 +0100 [thread overview]
Message-ID: <20080114221608.GA11732@basil.nowhere.org> (raw)
On a fresh object dir I get for a 32bit build:
make -C /home/lsrc/quilt/linux O=/home/lsrc/quilt/obj32
GEN /home/lsrc/quilt/obj32/Makefile
CHK include/linux/version.h
CHK include/linux/utsrelease.h
Using /home/lsrc/quilt/linux as source for kernel
CALL /home/lsrc/quilt/linux/scripts/checksyscalls.sh
CHK include/linux/compile.h
Building modules, stage 2.
MODPOST 1 modules
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
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
I think it worked on older object dirs where not everything was rebuild.
make --version
GNU Make 3.81
-Andi
next reply other threads:[~2008-01-14 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 22:16 Andi Kleen [this message]
2008-01-15 8:29 ` Latest git-x86 doesn't build on 32bit Ingo Molnar
2008-01-15 8:57 ` Ingo Molnar
2008-01-15 9:08 ` Andi Kleen
2008-01-15 10:01 ` 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=20080114221608.GA11732@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox