From: Paolo Ornati <javaman@katamail.com>
To: linux-kernel@vger.kernel.org
Subject: "make clean": how it's needed?
Date: Thu, 13 Mar 2003 15:56:07 +0100 [thread overview]
Message-ID: <20030313144624Z262367-25575+29577@vger.kernel.org> (raw)
I have this doubt, the "standard" procedure to build a kernel(2.2.x/2.4.x) is:
make menuconfig
make dep
make clean // ... when?
make modules
make bzImage
...
so, when I really _MUST_ run "make clean"?
always?
only after that I have applied a patch?
I think that many old "*.o" files are still good... and so, why I should
recompile them every time?
Bye,
Paolo
reply other threads:[~2003-03-13 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030313144624Z262367-25575+29577@vger.kernel.org \
--to=javaman@katamail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®