Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to rebuild following .config change?
Date: Tue, 23 Jun 2009 22:14:15 +0200	[thread overview]
Message-ID: <20090623201415.GC22116@mx.loc> (raw)
In-Reply-To: <h1rchh$9du$1@ger.gmane.org>

On Tue, Jun 23, 2009 at 08:05:06PM +0000, Grant Edwards wrote:
>Several times in the past week, I've gotten things terminally
>broken: where it's impossible to build after doing a "make
>menuconfig" or "make uclibc-menuconfg" and changing a
>configuration setting.
>
>It appears that you can't reliably make a configuration change
>and then do a "make".
>
>Doing a "make clean" doesn't appear to be enough either, since
>often a "make" still fails or doesn't rebuild certain things.
>
>You can do a "distclean", but then all the sources get
>re-downloaded and toolchains re-built -- which takes a _long_
>time.

if you set your DL_DIR != down then they are not wiped.
Alternatively you can rm -rf ${yourarch}_*, e.g.
rm -rf powerpc_nofpu_nommu_*
(or maybe not, not sure if Peter picked that convenience up already).
>
>How does one re-build appropriate packages after a
>configuration change.

My tree (search archives) has quite some improvements in this area,
perhaps you want to distill those out and submit it for review and
inclusion?

TIA and cheers,

  reply	other threads:[~2009-06-23 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 20:05 [Buildroot] How to rebuild following .config change? Grant Edwards
2009-06-23 20:14 ` Bernhard Reutner-Fischer [this message]
2009-06-24  7:13 ` Thomas Petazzoni
2009-06-25 19:02   ` Grant Edwards

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=20090623201415.GC22116@mx.loc \
    --to=rep.dot.nop@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