From: DevilKin <devilkin-lkml@blindguardian.org>
To: linux-kernel@vger.kernel.org
Subject: Correct path to compilation...
Date: Wed, 7 Aug 2002 16:44:44 +0200 [thread overview]
Message-ID: <200208071644.44361.devilkin-lkml@blindguardian.org> (raw)
Hello,
Little question: what is the correct path to compiling a kernel?
In the FAQ you find often:
make dep clean bzImage modules moduleS_install
Now, I, myself, have found that often (especially with -ac kernels) this
results in some file not being found...
Using
make clean dep ....
solves the problem.
What is the correct way?
Thanks!
DK
--
Shaw's Principle:
Build a system that even a fool can use, and only a fool will
want to use it.
reply other threads:[~2002-08-07 14:43 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=200208071644.44361.devilkin-lkml@blindguardian.org \
--to=devilkin-lkml@blindguardian.org \
--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®