All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Omer Sever <omer_sever@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Scheduler and Compilation
Date: Thu, 25 Oct 2001 23:48:58 +0200	[thread overview]
Message-ID: <20011025234858.A1550@werewolf.able.es> (raw)
In-Reply-To: <007501c15d68$94f12c60$8630fdd4@3232424>
In-Reply-To: <007501c15d68$94f12c60$8630fdd4@3232424>; from omer_sever@yahoo.com on Thu, Oct 25, 2001 at 17:20:25 +0200


On 20011025 Omer Sever wrote:
>     I have a project on Linux CPU Scheduler to make it Fair Share
>Scheduler.I will make some changes on some files such as sched.c vs...I will
>want to see the effect ot the change but recompilation of the kernel takes
>about half an hour on my machine.How can I minimize this time?Which part
>should I necessarily include in my config file for the kernel to minimize
>it?
>

Try this (and please tell me if it is worthy or I have to send it to trash)

--- linux-2.4.1-ac14/Makefile.org   Thu Feb 15 15:47:42 2001
+++ linux-2.4.1-ac14/Makefile   Thu Feb 15 15:48:11 2001
@@ -241,6 +241,9 @@
 
 
 include arch/$(ARCH)/Makefile
+
+CC:=$(CC)
+CPP:=$(CPP)
 
 export CPPFLAGS CFLAGS AFLAGS
 

--
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.14-pre1-beo #1 SMP Thu Oct 25 16:19:19 CEST 2001 i686

      parent reply	other threads:[~2001-10-25 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 15:20 Linux Scheduler and Compilation Omer Sever
2001-10-25 20:37 ` José Luis Domingo López
2001-10-25 19:06   ` Shaya Potter
2001-10-25 19:16     ` Richard B. Johnson
2001-10-25 23:07     ` george anzinger
2001-10-25 21:48 ` J . A . Magallon [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=20011025234858.A1550@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omer_sever@yahoo.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.