From: Tom Rini <trini@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: build failure for 2.6.11-mm2
Date: Thu, 10 Mar 2005 07:33:12 -0700 [thread overview]
Message-ID: <20050310143312.GO3098@smtp.west.cox.net> (raw)
In-Reply-To: <d10a9ba3f7ed768cff5f439840c96aec@freescale.com>
On Thu, Mar 10, 2005 at 08:06:04AM -0600, Kumar Gala wrote:
> right, but if you look back in the pervious -mm builds that past, they
> also did not have mkImage but still succeeded.
>
> It appear some change is now report the lack of mkImage as a build
> error. If this is desired behavior, should we maybe look at having a
> copy of its source in the kernel tree?
I think what's happened, but I haven't verified is that Andrew took an
incorrect patch to make 'mkuboot.sh', which invokes mkimage to produce a
uImage, fail if mkimage isn't found. This isn't right. The problem the
patch was trying to fix is that mkuboot.sh will say that it made a
uImage, even if mkimage isn't found.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2005-03-10 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 8:10 build failure for 2.6.11-mm2 Kumar Gala
2005-03-10 8:26 ` Eugene Surovegin
2005-03-10 14:06 ` Kumar Gala
2005-03-10 14:33 ` Tom Rini [this message]
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=20050310143312.GO3098@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.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).