From: Ron Eggler <reggler@semios.com>
To: buildroot@busybox.net
Subject: [Buildroot] build uboot for AT91SAM9G20
Date: Mon, 16 Dec 2013 01:52:44 +0000 [thread overview]
Message-ID: <3487466.tnqfWxcGWT@regdesktophome> (raw)
Hi,
I'm relatively new to buildroot, thus please excuse my beginner question.
I have configured buildroot to build an image for my AT91SAM9G20 system. I believe it has
built just fine but I'm running into an issue when it comes to uboot, I'm getting this:
...
make[1]: Entering directory `/etc/E10-buildroot/br2013.11/output/build/uboot-2013.10'
make: *** No rule to make target `e10_config'. Stop.
make[1]: *** [e10_config] Error 1
make[1]: Leaving directory `/etc/E10-buildroot/br2013.11/output/build/uboot-2013.10'
make: *** [/etc/E10-buildroot/br2013.11/output/build/uboot-2013.10/.stamp_configured]
Error 2
#
how can I get buildroot to properly compile uboot for my AT91SAM9G20?
Thanks,
Ron
--
*ron eggler | semios | senior software engineer*
320 - 887 Great Northern Way | Vancouver, BC | V5T 4T5
T | 604 229 2044 ext 105[1]
C | 778 230 9442[2]
E | reggler at semios.com[3]
smart farming[4]
twitter[5] linkedin[6]
--------
[1] tel:604%20229%202044%20ext%20105
[2] tel:778%20230%209442
[3] mailto:reggler at semios.com
[4] http://www.semios.com
[5] https://twitter.com/semios
[6] http://www.linkedin.com/company/semiosbio-technologies-inc?goback=%2Enmp_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1&trk=company_logo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131216/f22bd984/attachment.html>
next reply other threads:[~2013-12-16 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 1:52 Ron Eggler [this message]
2013-12-17 21:06 ` [Buildroot] build uboot for AT91SAM9G20 Arnout Vandecappelle
2013-12-17 21:20 ` Ron Eggler
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=3487466.tnqfWxcGWT@regdesktophome \
--to=reggler@semios.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