mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@gams.at>
To: steve.cameron@hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to speed up building of modules?
Date: Mon, 07 Apr 2003 00:09:03 +0200	[thread overview]
Message-ID: <7449.1049666943@frodo.gams.co.at> (raw)
In-Reply-To: Your message of "Fri, 04 Apr 2003 14:57:40 +0600." <20030404085740.GA10052@zuul.cca.cpqcorp.net>

Stephen Cameron <steve.cameron@hp.com> wrote:
>With all the distributions, and differnent
>offerings of distributions, and errata kernels... today, I count
>almost 40 distinct kernels we're trying to support, not counting the
>mainline development on kernel.org, and not counting multiple
>config file variations for each of those 40 or so kernels.
>
>The main catch seems to be the symbol checksums.  In order for those
>to match (and I'm not too interested in subverting those), the 
>config files used during the compile need to be very similar.  That 
>means building lots and lots of modules.  (Think about all the 
>modules which are enabled in redhat's typical default config files.)
>This takes time.  Mulitply 3 drivers * ~40 kernels * several config
>files, and pretty soon... well, pretty soon you don't remember
>what "preety soon" means.
[...]
>Any ideas?

http://ccache.samba.org/

	Bernd
-- 
Bernd Petrovitsch                              Email : bernd@gams.at
g.a.m.s gmbh                                  Fax : +43 1 205255-900
Prinz-Eugen-Straße 8                    A-1040 Vienna/Austria/Europe
                     LUGA : http://www.luga.at



  parent reply	other threads:[~2003-04-06 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04  8:57 Stephen Cameron
2003-04-04 21:17 ` Richard B. Johnson
2003-04-04 22:05   ` Robert White
2003-04-05  7:48 ` Sam Ravnborg
2003-04-06 22:09 ` Bernd Petrovitsch [this message]
2003-04-07 14:27 Cameron, Steve

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=7449.1049666943@frodo.gams.co.at \
    --to=bernd@gams.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.cameron@hp.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 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®