From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to rebuild following .config change?
Date: Tue, 23 Jun 2009 20:05:06 +0000 (UTC) [thread overview]
Message-ID: <h1rchh$9du$1@ger.gmane.org> (raw)
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.
How does one re-build appropriate packages after a
configuration change.
--
Grant Edwards grante Yow! If elected, Zippy
at pledges to each and every
visi.com American a 55-year-old
houseboy ...
next reply other threads:[~2009-06-23 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 20:05 Grant Edwards [this message]
2009-06-23 20:14 ` [Buildroot] How to rebuild following .config change? Bernhard Reutner-Fischer
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='h1rchh$9du$1@ger.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