From: Ben Dooks <ben@fluff.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARM EABI builds
Date: Tue, 26 Jun 2007 14:33:27 +0100 [thread overview]
Message-ID: <20070626133327.GA5989@trinity.fluff.org> (raw)
Has anyone had success with building an EABI buildroot? I have tried
building ARM (arm920t,gcc 4.1.2) and the image produced hangs (it
seems vfprintf does not work)
I have succesfully built images with gcc 4.1.2 and a patch to make it
build gcc with OABI.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next reply other threads:[~2007-06-26 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 13:33 Ben Dooks [this message]
2007-06-26 21:19 ` [Buildroot] ARM EABI builds Tom
2007-06-26 22:25 ` Ben Dooks
2007-06-27 8:19 ` Ben Dooks
2007-06-27 9:03 ` Konstantin Kletschke
2007-06-27 15:25 ` Ben Dooks
2007-06-27 17:44 ` Tom
2007-06-28 10:34 ` Ben Dooks
2007-06-28 19:13 ` Tom
2007-06-29 13:52 ` Ben Dooks
2007-06-28 22:50 ` Ulf Samuelsson
2007-06-28 23:57 ` Tom
2007-06-29 13:53 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2007-06-28 19:54 Stuart Wood
2007-06-28 23:01 ` Bernhard Fischer
2007-06-29 1:00 ` Tom
2007-06-29 9:31 ` Ben Dooks
2007-06-29 1:42 ` Alex Stewart
2007-06-29 7:16 ` Bernhard Fischer
2007-06-29 9:26 ` Ben Dooks
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=20070626133327.GA5989@trinity.fluff.org \
--to=ben@fluff.org \
--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