From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: yocto@yoctoproject.org
Subject: Re: Procedure to setup icecc for performing a distributed build
Date: Thu, 06 Sep 2012 16:38:21 +0100 [thread overview]
Message-ID: <1789113.10IpD71yH1@helios> (raw)
In-Reply-To: <5048C246.4090807@mlbassoc.com>
On Thursday 06 September 2012 09:33:26 Gary Thomas wrote:
> On 2012-09-06 09:29, Paul Eggleton wrote:
> > On Thursday 06 September 2012 19:23:53 Elvis Dowson wrote:
> >> Unfortunately no. I've got two machines, both with quad-core intel i7
> >> processors, but I just couldn't get icecc to work with yocto. I end up
> >> regularly perform fresh builds at least 5 to 6 times a day, and it takes
> >> me
> >> 2 hours to build core-image-minimal.
> >
> > At its core, icecc.bbclass just sets things up so that icecc is called
> > instead of the normal compiler. It would be worth verifying that that is
> > actually taking effect by looking at the commands being used as reported
> > in log.do_configure for specific recipes.
>
> Is this only for the host compiler or the target (cross) compilers as well?
> If it's only the host compiler being used for "native" builds, how much is
> there to be gained from distributing the work?
It covers all according to the comments at the top of the file.
I have to be honest and say I've never used icecc.bbclass; I've been told that
the overhead mostly wipes out any advantage of individual compile jobs being
farmed out to different machines, but I've never actually verified that first
hand.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-06 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 20:30 Procedure to setup icecc for performing a distributed build Elvis Dowson
2012-09-06 10:17 ` Paul Eggleton
2012-09-06 15:23 ` Elvis Dowson
2012-09-06 15:29 ` Paul Eggleton
2012-09-06 15:33 ` Gary Thomas
2012-09-06 15:38 ` Paul Eggleton [this message]
[not found] ` <5048C1C2.1010903@mlbassoc.com>
2012-09-06 17:52 ` Elvis Dowson
2012-09-06 21:46 ` Dmitry Eremin-Solenikov
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=1789113.10IpD71yH1@helios \
--to=paul.eggleton@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 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.