From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain
Date: Thu, 29 Apr 2010 12:07:00 +0200 [thread overview]
Message-ID: <20100429120700.45af880e@surf> (raw)
In-Reply-To: <hqn0op$14i$1@dough.gmane.org>
On Wed, 21 Apr 2010 14:06:18 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I never do anything with buildroot other than complete ground-up
> builds from scratch. Despite the documented ways to do partial
> rebuilds, I was never able to reliably do a parial rebuild. After
> several instances of spending hours or days chasing problems that went
> away after a complete re-build, I simply gave up on doing anything
> other than building from zero.
Yes, building from zero is the only way of being sure of what is
happening. As soon as *any* system-wide change, such as a toolchain
configuration change, is made, then a rebuild from zero is needed.
Partial rebuilds, as documented in the documentation, are possible on a
per-package basis, when you fully understand what you're doing and how
Buildroot uses the stamp files. You can very easily break things, or on
the opposite, get something working that wouldn't work with a build
starting from zero.
When doing work on packages, I do use partial rebuilds a lot, but I
also make sure to do a full rebuild at the end to make sure everything
is in order.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-04-29 10:07 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 ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Peter Korsgaard
2010-04-29 10:03 ` Thomas Petazzoni
2010-04-29 10:07 ` Thomas Petazzoni [this message]
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=20100429120700.45af880e@surf \
--to=thomas.petazzoni@free-electrons.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