From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <linuxppc-dev@ozlabs.org>,
"Buildroot Mailinglist, " <buildroot@uclibc.org>
Subject: Re: zImage.embedded
Date: Mon, 14 Apr 2008 18:05:52 +0200 [thread overview]
Message-ID: <01e801c89e49$6d0e6400$ad289e86@LPSC0173W> (raw)
In-Reply-To: fa686aa40804110655x48120e84tde01a52d8bb39a3@mail.gmail.com
[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/
next prev parent reply other threads:[~2008-04-14 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 13:43 zImage.embedded Guillaume Dargaud
2008-04-11 13:55 ` zImage.embedded Grant Likely
2008-04-11 15:51 ` zImage.embedded Guillaume Dargaud
2008-04-11 16:04 ` zImage.embedded Grant Likely
2008-04-14 16:05 ` Guillaume Dargaud [this message]
2008-04-14 20:55 ` [Buildroot] zImage.embedded Ulf Samuelsson
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='01e801c89e49$6d0e6400$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--cc=buildroot@uclibc.org \
--cc=linuxppc-dev@ozlabs.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).