From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] uImage build error
Date: Fri, 27 Aug 2010 10:01:25 +0200 [thread overview]
Message-ID: <20100827100125.21e2ccc8@surf> (raw)
In-Reply-To: <C43529A246480145B0A6D0234BDB0F0D481DAD@MELANITE.micrel.com>
Hello David,
On Thu, 26 Aug 2010 17:26:09 -0700
"Choi, David" <David.Choi@Micrel.Com> wrote:
> Thank you for your e-mail. Basically I understand Buildroot is an
> independent from linux kernel, as you pointed out in your previous
> e-mail.
>
> The reason I posted the question is that users can select [kernel
> binary format] from [make menuconfig] in the buildroot of
> v2010.08-rc1.
>
> As I need u-boot and linux kernel, I put the need information properly
> from the [make menuconfig]. When I choose vmlinux as a kernel binary
> format,
>
> I can see the root file system, kernel and u-boot in the output/image
> direcoty(rootfs.initcramfs, u-boot.bin and vmlinux.bin).
>
> But when I change uImage as a kernel binary format, there is an error
> message( make[1]: ***No rule to make target uImage. Stop).
From your previous post, I understand that you are building for MIPS.
However, the kernel doesn't provide a "make uImage" target for the MIPS
architecture: you have to produce the mkimage'd kernel manually.
On the Buildroot side, we should just prevent you from selecting
"uImage" if the architecture does not support it.
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-08-27 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 21:41 [Buildroot] uImage build error Choi, David
2010-08-25 21:54 ` Marcus Osdoba
2010-08-27 0:26 ` Choi, David
2010-08-27 8:01 ` Thomas Petazzoni [this message]
2010-08-27 14:40 ` Choi, David
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=20100827100125.21e2ccc8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox