From: Loc Nguyen <it050021@gmail.com>
To: barebox@lists.infradead.org
Subject: Issue when building Barebox with ARM EABI 4.4.3
Date: Wed, 02 Nov 2011 19:03:33 +0700 [thread overview]
Message-ID: <4EB13195.9060004@gmail.com> (raw)
In-Reply-To: <20111102101652.GK23421@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 318 bytes --]
Hi all,
After building Barebox with arm-eabi 4.4.3, Barebox start-up properly
but I got "command not found" error. I checked system.map and found that
there is no API from//command/ folder.
But everything is OK with arm-eabi 4.4.0.
So I think the problem comes from 4.4.3 ?
Anyone can help me ?
Best regards,
LocN
[-- Attachment #1.2: Type: text/html, Size: 652 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-11-02 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 17:43 Failed to launch barebox from flash memory on i.MX35 Peter
2011-11-02 10:16 ` Sascha Hauer
2011-11-02 12:03 ` Loc Nguyen [this message]
2011-11-02 14:04 ` Peter Kuennemann@Crane-Soft
2011-11-02 14:49 ` Sascha Hauer
2011-11-02 14:58 ` Peter Kuennemann@Crane-Soft
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=4EB13195.9060004@gmail.com \
--to=it050021@gmail.com \
--cc=barebox@lists.infradead.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