mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven-Haegar Koch <haegar@sdinet.de>
To: Alessio Igor Bogani <abogani@texware.it>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Suggestions request for speed-up kernel compilation
Date: Fri, 24 Apr 2009 12:37:41 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.00.0904241235040.12781@aurora.sdinet.de> (raw)
In-Reply-To: <63a49ef40904240257w45cc9c03n6e71ff4e4f69209b@mail.gmail.com>

On Fri, 24 Apr 2009, Alessio Igor Bogani wrote:

> I'm a kernel newbie and I would be very happy to receive some tips
> about kernel compilation from experienced developers.
> 
> I have recently elaborated some trivial patches. For each one I have
> done a build test at minimum and I find myself spend a lot of time
> waiting my Core Duo to accomplish this task. Make is a very smart tool
> but after a git pull or a git fetch origin/git reset --hard origin it
> can't help as desired.
> 
> Unfortunately I don't have a clustered compilation farm under my control. :-)
> 
> Anyone can suggest me how mitigate that issue?

What helps me with this is using ccache (compiler cache) - it keeps the 
compile results inside a cache and when compiling the same file again it 
fetches the result from there.

on debian it is just:
  apt-get install ccache
  export PATH=/usr/lib/ccache:$PATH
  ...work on kernel like normal...


c'ya
sven

-- 
The lights are fading out, once more...

  reply	other threads:[~2009-04-24 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24  9:57 Alessio Igor Bogani
2009-04-24 10:37 ` Sven-Haegar Koch [this message]
2009-04-24 10:38 ` Sam Ravnborg
2009-04-24 11:59 ` Richard Kennedy
2009-04-24 14:02 ` Al Viro
2009-04-25  7:54 ` Andi Kleen

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.DEB.2.00.0904241235040.12781@aurora.sdinet.de \
    --to=haegar@sdinet.de \
    --cc=abogani@texware.it \
    --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®