Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARM EABI toolchain - anyone build it successfully?
Date: Tue, 19 Aug 2008 17:34:42 +0200	[thread overview]
Message-ID: <48AAE812.4020706@wpkg.org> (raw)

I'm trying to make ARM EABI toolchain using the latest snapshot of 
Buildroot.
However, no matter which options I use (thread library implementation, 
uClibc version etc.) I'm only able to build GCC (4.3.1).

Then, it breaks later on on building uClibc.

I also tried building uClibc from nptl branch, but it also failed.

As different thread library implementations and uClibc versions give 
different errors, I won't paste it here, unless requested.

So my question - did anyone manage to build ARM EABI toolchain with 
buildroot (GCC 4.3.1 + uClibc; I also need busybox)?


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2008-08-19 15:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 15:34 Tomasz Chmielewski [this message]
2008-08-19 15:49 ` [Buildroot] ARM EABI toolchain - anyone build it successfully? Bernhard Reutner-Fischer
2008-08-19 15:54   ` Tomasz Chmielewski
2008-08-19 16:28     ` Bernhard Reutner-Fischer
2008-08-20  9:29       ` Tomasz Chmielewski
2008-08-20  9:49         ` Bernhard Reutner-Fischer
2008-08-20  9:55           ` Tomasz Chmielewski
2008-08-20 10:07           ` Tomasz Chmielewski
2008-08-20 10:16             ` Bernhard Reutner-Fischer
2008-08-20 10:22               ` Tomasz Chmielewski
2008-08-20 10:59               ` Tomasz Chmielewski
2008-08-20 11:24                 ` Tomasz Chmielewski
2008-08-20 10:00         ` Tomasz Chmielewski
2008-08-20 10:21           ` Bernhard Reutner-Fischer

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=48AAE812.4020706@wpkg.org \
    --to=mangoo@wpkg.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