Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Still can't build workingrootfswith	crosstool-NGtoolchain
Date: Wed, 21 Apr 2010 18:33:02 +0000 (UTC)	[thread overview]
Message-ID: <hqngcu$47r$1@dough.gmane.org> (raw)
In-Reply-To: 8035C465416D4C9D8992B2CB364F236E@development

On 2010-04-21, Microbit_P43000 <microbit@virginbroadband.com.au> wrote:

> Indeed, the time I mention is a complete make from scratch.
> Xcompiler, utils, libc, busybox, rootfs, etc.... It doesn't have to
> include the kernel, that takes all but 5 mins. This is on a P4 dual
> CPU 3 GHz (albeit with only 1 GB ram).

The toolchain is probably 90+ percent of that.  I think you'll be far
happier if you use an external toolchain.

> I've tried external tools like codesourcery (which I dislike) and
> arm-elf-gcc and likes. Either I ran into sysroot problems, or their
> were hissies being thrown about 90% through building, that sort of
> stuff - yet again off a Sherlock Holmes to figure out in scripts
> where these mysterious 'issues' come from.

AFAIK, most of the buildroot developers use external toolchains built
by crosstools-NG (and that's what I'm now using), so that's probably
the path of least resistance.  If you like, I can send you the
crosstools-NG and uClibc config files I'm using for ARM9, but 
Crosstools-NG comes with quite a few sample configs -- one of them is
probably pretty close to what you want.

Just pay close attention to ARM EABI vs. OABI.

-- 
Grant Edwards               grant.b.edwards        Yow! As President I have
                                  at               to go vacuum my coin
                              gmail.com            collection!

  reply	other threads:[~2010-04-21 18:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 14:44 [Buildroot] Still can't build working rootfs with crosstool-NG toolchain Grant Edwards
2010-04-19 16:06 ` Thomas Petazzoni
2010-04-19 18:08   ` Grant Edwards
2010-04-19 17:50 ` Peter Korsgaard
2010-04-19 18:13   ` Grant Edwards
2010-04-20 18:26 ` [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain Microbit_P43000
2010-04-20 23:43   ` Ben Kloosterman
2010-04-21  8:15     ` Microbit_P43000
2010-04-21 14:06       ` Grant Edwards
2010-04-21 16:07         ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 16:31           ` Grant Edwards
2010-04-21 18:25             ` [Buildroot] Still can't build workingrootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 18:33               ` Grant Edwards [this message]
2010-04-21 18:46                 ` Peter Korsgaard
2010-04-21 22:06                 ` [Buildroot] Still can't buildworkingrootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 18:43             ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Peter Korsgaard
2010-04-29 10:03             ` Thomas Petazzoni
2010-04-29 10:07         ` [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain Thomas Petazzoni

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='hqngcu$47r$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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