linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* build failure for 2.6.11-mm2
@ 2005-03-10  8:10 Kumar Gala
  2005-03-10  8:26 ` Eugene Surovegin
  0 siblings, 1 reply; 4+ messages in thread
From: Kumar Gala @ 2005-03-10  8:10 UTC (permalink / raw)
  To: Tom Rini; +Cc: linuxppc-dev list

Tom,

Do you have any ideas on what changes occurred in the makefiles to 
cause the uImage related failures:

http://l4x.org/k/?d=2173

- kumar

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: build failure for 2.6.11-mm2
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Eugene Surovegin @ 2005-03-10  8:26 UTC (permalink / raw)
  To: Kumar Gala; +Cc: Tom Rini, linuxppc-dev list

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: build failure for 2.6.11-mm2
  2005-03-10  8:26 ` Eugene Surovegin
@ 2005-03-10 14:06   ` Kumar Gala
  2005-03-10 14:33     ` Tom Rini
  0 siblings, 1 reply; 4+ messages in thread
From: Kumar Gala @ 2005-03-10 14:06 UTC (permalink / raw)
  To: Eugene Surovegin; +Cc: Tom Rini, linuxppc-dev list

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: build failure for 2.6.11-mm2
  2005-03-10 14:06   ` Kumar Gala
@ 2005-03-10 14:33     ` Tom Rini
  0 siblings, 0 replies; 4+ messages in thread
From: Tom Rini @ 2005-03-10 14:33 UTC (permalink / raw)
  To: Kumar Gala; +Cc: linuxppc-dev list

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/

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-03-10 14:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).