public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Some problems with 2.6.13.4
Date: Tue, 25 Oct 2005 01:27:15 +0900	[thread overview]
Message-ID: <djj24d$ja8$1@sea.gmane.org> (raw)
In-Reply-To: <20051015203824.GN12774@schottelius.org>

Nico Schottelius wrote:
> Jesper Juhl [Sat, Oct 15, 2005 at 10:22:22PM +0200]:
> 
>>On 10/15/05, Nico Schottelius <nico-kernel@schottelius.org> wrote:
>>[snip]
>>
>>>Could we somehow debug this differently or do I have to install
>>>2.6.13.2 and 2.6.13.1, too? It would take simply hours until it is
>>>finished here.
>>>
>>
>>If you have another, faster, machine available you could build the
>>kernel(s) on that one.
> 
> Actually, one of my fastest machines is this one:
> 
> bruehe2# cat /proc/cpuinfo 
> [...]
> model name      : Pentium III (Katmai)
> cpu MHz         : 551.280
> [...]
> 
> And one, which has a not-so-good connection to me.
> 
> 
>>You don't have to build a kernel on the same
>>machine that is later supposed to run it.
> 
> 
> That's clear :-)
> 
> 
>>Also, if you have more than one machine (even if they are not
>>especially fast) then you can use distcc (http://distcc.samba.org/) to
>>distribute the build over multiple machines which can speed up a build
>>a great deal.
> 
> 
> distcc will fail here, because of different gccs and different distributions
> (ever tried to use gentoo and distcc in the same distcc-network? It's a real
> pain).
How come?
I am using distcc + ccache in default install with at least -j5 on my network of Gentoo machines.
And building a kernel with -j8 on 4 boxen (P4@2GHz each) is a snap.
Particularly pleasing to watch distccmon-gui :-D

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|


  parent reply	other threads:[~2005-10-24 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 12:21 Some problems with 2.6.13.4 Nico Schottelius
2005-10-15 15:05 ` Christian Kujau
2005-10-15 15:40   ` Nico Schottelius
2005-10-15 20:02     ` Nico Schottelius
2005-10-15 20:22       ` Jesper Juhl
2005-10-15 20:38         ` Nico Schottelius
2005-10-15 21:03           ` Paolo Ornati
2005-10-24 16:27           ` Kalin KOZHUHAROV [this message]
2005-10-16 11:19       ` Nico Schottelius

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='djj24d$ja8$1@sea.gmane.org' \
    --to=kalin@thinrope.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