All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Still can't build working rootfswith	crosstool-NGtoolchain
Date: Wed, 21 Apr 2010 20:43:59 +0200	[thread overview]
Message-ID: <87sk6o7ij4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <hqn98s$5sn$1@dough.gmane.org> (Grant Edwards's message of "Wed,  21 Apr 2010 16:31:24 +0000 (UTC)")

>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:

Hi,

 >> 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.

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

FYI, I do full builds (internal toolchain including C++, a number of
packages including Qt, U-Boot and Linux kernel) in about 25 mins on a
2.8GHz i7 (buildbot server)

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

Agreed. Doing these things with BR is mainly interesting as a
structured integration tool when the basics are stable - E.G. to ensure
you have everything under configuration control and can reproduce the
build.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-04-21 18:43 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
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             ` Peter Korsgaard [this message]
2010-04-29 10:03             ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain 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=87sk6o7ij4.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.