From: Mark Glines <mark@glines.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?
Date: Sun, 24 Dec 2006 13:28:59 -0800 [thread overview]
Message-ID: <458EF11B.5030509@glines.org> (raw)
In-Reply-To: <fa.tciB/Sye1gyFArGtVgaZAmdArxQ@ifi.uio.no>
Linus Torvalds wrote:
> (much of the latter syntactic cleanups). And arm and powerpc updates.
Hmm. I'm trying to build 2.6.20-rc2 on a little powerpc box with
arch/powerpc/configs/linkstation_defconfig, and I get:
paranoid@kuro-2 /usr/src/linux $ make zImage
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
[snip lots of buildspam]
LD lib/zlib_deflate/built-in.o
LD lib/zlib_inflate/built-in.o
GEN .version
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
MODPOST vmlinux
ln: accessing `arch/powerpc/boot/zImage': No such file or directory
make[1]: *** [arch/powerpc/boot/zImage] Error 1
make: *** [zImage] Error 2
So, uh, are we forgetting to go into the right subdirectory to make the
actual zImage, or what? If I'm just doing something wrong, I'd love to
know what it is.
I'll follow up here on lkml if I diagnose this further. Thanks,
Mark
next parent reply other threads:[~2006-12-24 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.tciB/Sye1gyFArGtVgaZAmdArxQ@ifi.uio.no>
2006-12-24 21:28 ` Mark Glines [this message]
[not found] <fa.ne7N9dqjDz5qS4D/fowPKdPc4ZY@ifi.uio.no>
[not found] ` <fa.pM17YEcICUlveSt/vbSKGv6sFWk@ifi.uio.no>
2006-12-25 19:45 ` Linux 2.6.20-rc2: forgot how to make a zImage on powerpc? Mark Glines
2006-12-25 20:31 ` Guennadi Liakhovetski
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=458EF11B.5030509@glines.org \
--to=mark@glines.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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