All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] uImage could not be built before and after big bootloader patch
Date: Sat, 19 Jun 2010 13:34:46 +0200	[thread overview]
Message-ID: <20100619133446.2123896f@surf> (raw)
In-Reply-To: <4C1BE51D.5040406@gmx.net>

Hello,

On Fri, 18 Jun 2010 23:29:01 +0200
Ossy <ossy1980@gmx.net> wrote:

> I am still not able to make a U-Boot image (uImage) of the linux kernel 
> if I use "Same version as kernel headers". U-Boot is built before trying 
> to make the uImage, but it still gives the following error:
> 
> ...
> "mkimage" command not found - U-Boot images will not be built
> ...
> 
> Am I forced to install U-Boot (meaning mkimage) on the host?
> This is not neccessary if using "Advanced configuration".

Is this a regression of the bootloaders-cleanup branch ? As far as I
can see the non-Advanced configuration for the kernel never handled the
dependency on host mkimage. So I think it wasn't working before, and it
still isn't working.

I have another branch, linux-cleanup, that reworks all the code that
builds the kernel, so I'm really interested in improving the existing
code (of course, if it's a regression, I'll fix it).

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-06-19 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 21:29 [Buildroot] uImage could not be built before and after big bootloader patch Ossy
2010-06-19 11:34 ` Thomas Petazzoni [this message]
     [not found]   ` <4C1CC857.50309@gmx.net>
2010-06-19 15:12     ` Thomas Petazzoni
2010-06-19 16:43       ` Thomas Petazzoni

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=20100619133446.2123896f@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.