From: jlnance@intrex.net
To: linux-kernel@vger.kernel.org
Subject: Re: Compiling kernel
Date: Wed, 2 May 2001 20:52:02 -0400 [thread overview]
Message-ID: <20010502205202.A18296@bessie.localdomain> (raw)
In-Reply-To: <65256A40.00441BB5.00@sandesh.hss.hns.com>
In-Reply-To: <65256A40.00441BB5.00@sandesh.hss.hns.com>; from alad@hss.hns.com on Wed, May 02, 2001 at 06:00:00PM +0530
On Wed, May 02, 2001 at 06:00:00PM +0530, alad@hss.hns.com wrote:
> suppose I am making some change in sched.c and now I want to build my kernel
> that reflects the change..
> Is there any way I can avoid answering all the questions when I do make zImage ?
>
> In short how should I compile the kernel (in very small time) to see my changes.
It sounds like you are running "make config" after you make your changes.
If you run "make oldconfig" instead of "make config" it will not ask you
questions unless you have added config options to the configure scripts.
Its probably not necessary to run either on of these if you have just made
minor changes to the code. It does not hurt to do it though, and
"make oldconfig" is fast.
Hope this helps,
Jim
prev parent reply other threads:[~2001-05-03 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 12:30 alad
2001-05-02 13:12 ` Anton Altaparmakov
2001-05-03 0:52 ` jlnance [this message]
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=20010502205202.A18296@bessie.localdomain \
--to=jlnance@intrex.net \
--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®