From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Reducing buildroot compile times by reusing toolchain?
Date: Tue, 30 Sep 2014 11:58:56 -0500 [thread overview]
Message-ID: <20140930115856.6d378af9@core2quad.morethan.org> (raw)
In-Reply-To: <A2A6A18A7161D44FBCA90D5B3AF90A2E5A484CBB@AMEHLEX02.ehl.pri>
On Tue, 30 Sep 2014 15:04:56 +0000
"Paassen, Hiram van" <Hiram.van.Paassen@mastervolt.com> wrote:
> Our build using eglibc, systemd and python takes (including toolchain)
> 45 min on my i7 quad-core laptop. At least half of that seems to be
> the toolchain and other "host" tools. I prefer a faster machine but I
> suspect my boss won't give that to me given that I already have the
> fastest machine in the office.
>
That might be I/O limited -
Get Boss to buy you a server-grade, fast, SSD for the laptop.
next prev parent reply other threads:[~2014-09-30 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 8:02 [Buildroot] Reducing buildroot compile times by reusing toolchain? Paassen, Hiram van
2014-09-30 9:30 ` Thomas Petazzoni
2014-09-30 9:34 ` Richard Braun
2014-09-30 15:04 ` Paassen, Hiram van
2014-09-30 16:58 ` Mike Zick [this message]
2014-09-30 17:12 ` Thomas Petazzoni
2014-09-30 9:41 ` Thomas De Schampheleire
2014-09-30 10:11 ` Károly Kasza
2014-09-30 15:10 ` Paassen, Hiram van
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=20140930115856.6d378af9@core2quad.morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/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