From: Kumar Gala <kumar.gala@freescale.com>
To: "Eugene Surovegin" <ebs@ebshome.net>
Cc: Tom Rini <trini@kernel.crashing.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: build failure for 2.6.11-mm2
Date: Thu, 10 Mar 2005 08:06:04 -0600 [thread overview]
Message-ID: <d10a9ba3f7ed768cff5f439840c96aec@freescale.com> (raw)
In-Reply-To: <20050310082639.GA19275@gate.ebshome.net>
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?
- kumar
On Mar 10, 2005, at 2:26 AM, Eugene Surovegin wrote:
> On Thu, Mar 10, 2005 at 02:10:04AM -0600, Kumar Gala wrote:
> > Do you have any ideas on what changes occurred in the makefiles to
> > cause the uImage related failures:
> >
> > http://l4x.org/k/?d=2173
>
> This looks like mkimage is just not present on build host. I don't
> think it's included anywhere in kernel tree, so it must be installed
> separately.
>
> --
> Eugene
next prev parent reply other threads:[~2005-03-10 14:06 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 [this message]
2005-03-10 14:33 ` Tom Rini
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=d10a9ba3f7ed768cff5f439840c96aec@freescale.com \
--to=kumar.gala@freescale.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).