From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] zImage.embedded
Date: Mon, 14 Apr 2008 22:55:03 +0200 [thread overview]
Message-ID: <000b01c89eb5$2af81630$070514ac@atmel.com> (raw)
In-Reply-To: 01e801c89e49$6d0e6400$ad289e86@LPSC0173W
> [cross posting from one mailing list to another]
>
>>> is the file zImage.elf my proper network image ?
>>
>> What bootloader is on your board? zImage.elf *might* be the proper
>> image. If you're using u-boot, then you want to build a uImage
>> instead.
>
> I'm trying to compile u-boot with buildroot, but it fails with:
>
> /usr/bin/make -j1 -C
> /home/guinevere/Min_UartLite_NetLite_Ace/buildroot/project_build_powerpc/genepy/u-boot-1.3.2
> \
> ""_config
> make[1]: Entering directory
> `/home/guinevere/Min_UartLite_NetLite_Ace/buildroot/project_build_powerpc/genepy/u-boot-1.3.2'
> make[1]: *** No rule to make target `_config'. Stop.
> make[1]: Leaving directory
> `/home/guinevere/Min_UartLite_NetLite_Ace/buildroot/project_build_powerpc/genepy/u-boot-1.3.2'
> make: ***
> [/home/guinevere/Min_UartLite_NetLite_Ace/buildroot/project_build_powerpc/genepy/u-boot-1.3.2/.configured]
> Error 2
>
> Apparently it expects a BOARD_NAME variable, but I don't know what to put in
> it (I looked at the makefile and can't find the ml405 referenced in there).
> --
> Guillaume Dargaud
> http://www.gdargaud.net/
>
I think you need to figure out how to build u-boot for your board
outside buildroot, before you try to build it inside buildroot.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-04-14 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <014701c89bda$09380060$ad289e86@LPSC0173W>
[not found] ` <fa686aa40804110655x48120e84tde01a52d8bb39a3@mail.gmail.com>
2008-04-14 16:05 ` [Buildroot] zImage.embedded Guillaume Dargaud
2008-04-14 20:55 ` Ulf Samuelsson [this message]
2008-04-15 9:33 ` Guillaume Dargaud
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='000b01c89eb5$2af81630$070514ac@atmel.com' \
--to=ulf.samuelsson@atmel.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