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 working rootfswith	crosstool-NGtoolchain
Date: Wed, 21 Apr 2010 16:31:24 +0000 (UTC)	[thread overview]
Message-ID: <hqn98s$5sn$1@dough.gmane.org> (raw)
In-Reply-To: 82069254E03F44CB90EDB741DB18CBF9@development

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

> That puts my soul at rest a bit... &:). Wish I posted this many
> months ago, oh well... I have a copy of the 'dl' dir, re-extract BR,
> re-copy the dl directory contents and re-import my configs for
> everything and make.
>
> At one stage the whole cycle took ~ 1 hour 15 mins. Common sense had
> to prevail I guess - it's just a lot faster than chasing ghosts - it
> seems that your experience matches the observations I made.

If it's taking that long, I suspect you're also building a toolchain
and kernel everytime.  When I realized that partial rebuilds weren't
practical, I switched to using an external toolchain.  With an
external toolchain and an external download directory, doing a
from-scratch basic rootfs build takes about 6-7 minutes on a single
CPU, 2GHz AMD Athlon64.

I also switched to building my kernel outside of buildroot.  If you're
doing any sort of kernel development (or just want to try
experimenting with kernel configurations), doing the kernel builds
with buildroot is pretty clumsy.

Once you've got a kernel configuration figured out and set in stone,
it could be useful to have the kernel built by buildroot, but it
doesn't seem to be a paractical way to do kernel development.

-- 
Grant Edwards               grant.b.edwards        Yow! PARDON me, am I
                                  at               speaking ENGLISH?
                              gmail.com            

  reply	other threads:[~2010-04-21 16:31 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 [this message]
2010-04-21 18:25             ` [Buildroot] Still can't build workingrootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 18:33               ` Grant Edwards
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='hqn98s$5sn$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