From: Robert P. J. Day <rpjday@crashcourse.ca>
To: buildroot@busybox.net
Subject: [Buildroot] make clean not so clean
Date: Fri, 1 Feb 2008 03:34:17 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802010333120.8154@localhost.localdomain> (raw)
In-Reply-To: <1201844203.3526.46.camel@localhost.localdomain>
On Fri, 1 Feb 2008, Ormund Williams wrote:
> On Thu, 2008-01-31 at 21:02 -0800, jake sullivan wrote:
> > I'm not sure how to go about fixing this, but I have been able to
> > recreate an annoying little bug (that I think is the source of a
> > number of other newb problems).
> >
> ...(snip)...
> > My gut says to update "make clean" to delete all the config files (and
> > basically everything but the source files), but before I put work into
> > making and testing a patch, I want to make sure that is the right
> > approach...
> >
> Don't know about "Right Appraach", but I just locate my download
> directory outside the Buildroot tree.
>
> Under: Build Options --->
>
> $(BASE_DIR)/../dl) Download dir
to save me the trouble of pawing through the source, if you override
the default download directory (of "dl"?), does that mean a "make
distclean" will leave all the downloads alone? thanks.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca
Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================
next prev parent reply other threads:[~2008-02-01 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 5:02 [Buildroot] make clean not so clean jake sullivan
2008-02-01 5:36 ` Ormund Williams
2008-02-01 8:20 ` Bernhard Fischer
2008-02-01 9:40 ` Robert P. J. Day
2008-02-01 8:34 ` Robert P. J. Day [this message]
2008-02-01 8:46 ` Ormund Williams
2008-02-01 9:15 ` Robert P. J. Day
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=alpine.LFD.1.00.0802010333120.8154@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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