From: David Woodhouse <dwmw2@infradead.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Merge dtc
Date: Wed, 05 Dec 2007 00:54:38 +0000 [thread overview]
Message-ID: <1196816078.13978.411.camel@pmac.infradead.org> (raw)
In-Reply-To: <1196807633.13978.383.camel@pmac.infradead.org>
On Tue, 2007-12-04 at 22:33 +0000, David Woodhouse wrote:
> Make vmlinux the default target instead of zImage would seem like a
> better answer. I'm surprised that it isn't like that already, in fact --
> and I'm only inferring that it isn't from your message. I always thought
> that if I typed 'make' I got the vmlinux and not a zImage.
Ooh, no -- I don't. I get an error, and I never even noticed...
WRAP arch/powerpc/boot/zImage.chrp
WRAP arch/powerpc/boot/zImage.pmac
WRAP arch/powerpc/boot/cuImage.52xx
/pmac/git/libertas-2.6/arch/powerpc/boot/wrapper: line 257: mkimage: command not found
make[1]: *** [arch/powerpc/boot/cuImage.52xx] Error 127
I'd be perfectly happy with 'make vmlinux then' as a response to anyone
who complains. And in fact since it'll correctly make the vmlinux and
_then_ fail to create the zImage, I would have thought that anyone with
even a modicum of common sense will _notice_ that, and start using
'make vmlinux' all by themselves without prompting.
--
dwmw2
next prev parent reply other threads:[~2007-12-05 0:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 5:02 Merge dtc David Gibson
2007-10-16 5:08 ` Kumar Gala
2007-10-16 5:18 ` David Gibson
2007-10-16 5:39 ` Paul Mackerras
2007-10-16 5:50 ` Kumar Gala
2007-10-16 6:01 ` Benjamin Herrenschmidt
2007-10-16 6:23 ` Kumar Gala
2007-10-16 10:53 ` Josh Boyer
2007-10-17 19:59 ` Timur Tabi
2007-10-17 20:12 ` Josh Boyer
2007-10-17 20:31 ` Grant Likely
2007-10-17 21:42 ` Linas Vepstas
2007-10-17 21:51 ` Jon Loeliger
2007-10-16 6:00 ` Benjamin Herrenschmidt
2007-10-16 6:24 ` Kumar Gala
2007-10-16 13:17 ` Grant Likely
2007-10-16 13:41 ` Kumar Gala
2007-10-17 5:22 ` David Gibson
2007-10-17 13:15 ` Grant Likely
2007-10-17 16:22 ` Stephen Neuendorffer
2007-12-04 1:59 ` David Woodhouse
2007-12-04 3:10 ` David Gibson
2007-12-04 17:22 ` David Woodhouse
2007-12-04 13:25 ` Jon Loeliger
2007-12-04 15:26 ` Josh Boyer
2007-12-04 16:04 ` Kumar Gala
2007-12-04 22:12 ` David Gibson
2007-12-04 16:08 ` Scott Wood
2007-12-04 22:21 ` Paul Mackerras
2007-12-04 22:33 ` David Woodhouse
2007-12-05 0:54 ` David Woodhouse [this message]
2007-12-05 1:49 ` Josh Boyer
2007-12-05 1:09 ` Paul Mackerras
2007-12-04 22:34 ` Josh Boyer
2007-12-05 2:22 ` Paul Mackerras
2007-12-05 2:26 ` Josh Boyer
2007-12-05 4:00 ` Josh Boyer
2007-12-05 4:37 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 17:49 Milton Miller
2007-10-18 19:59 ` Sam Ravnborg
2007-10-19 1:45 ` David Gibson
2007-10-19 5:56 ` Milton Miller
2007-10-19 6:55 ` David Gibson
2007-10-19 7:07 ` Sam Ravnborg
2007-10-19 7:10 ` David Gibson
2007-10-19 18:42 ` Sam Ravnborg
2007-10-31 2:45 ` David Gibson
2007-11-08 13:59 ` Jon Loeliger
2007-10-19 1:30 ` David Gibson
2007-10-19 5:34 ` Milton Miller
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=1196816078.13978.411.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).