From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Sat, 14 Jun 2014 09:57:43 +0200 [thread overview]
Message-ID: <20140614095743.4b60810d@free-electrons.com> (raw)
In-Reply-To: <CAE9DZUQhgXHBpRQX1Gzde3x4uOgXTHdqS3=b2pc7f6KCdD1jPg@mail.gmail.com>
Dear Dallas Clement,
(Seems like your e-mail client has major issues with line wrapping).
On Fri, 13 Jun 2014 19:52:15 -0500, Dallas Clement wrote:
> Fabio, I have some good news! I had commented out the .NOTPARALLEL
> in the top-level
> makefile earlier, but I was not setting BR2_JLEVEL correctly, as I was
> doing so from
> a wrapper makefile. Anyhow, parallel building is working for me now
> after fixing my mistake.
> When I started this journey, my build times were about 1 hour and 50
> minutes. After
> enabling ccache they were reduced to about 1 hour. With parallel
> package building,
> all 8 of my CPU cores are near 100% the whole time, and build times
> are now only 14 minutes!!!
>
> You are a beautiful man! Thank you for all you have done to get this
> working.
That's indeed a very significant improvement. However, be careful that
using top-level parallel builds makes builds non-reproducible: we do
not guarantee that from one build to the other you'll get the same
result. You might even get failures sometimes, and then success. Or the
other way around. That's why we don't allow top-level parallel build by
default.
Unfortunately, the only way to fix this is to have per-package sysroot,
and doing this will involve a lot more preparation work before starting
the build of each package, which will certainly reduce the benefit of
top-level parallel build. That's something that needs to be worked on,
but it's far from being a trivial problem.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-14 7:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 16:34 [Buildroot] autoconf caching Dallas Clement
2014-06-05 17:05 ` Baruch Siach
2014-06-05 17:34 ` Yann E. MORIN
2014-06-05 17:39 ` Dallas Clement
2014-06-05 18:57 ` Yann E. MORIN
2014-06-05 20:42 ` Thomas Petazzoni
2014-06-05 22:06 ` Dallas Clement
2014-06-06 6:13 ` Thomas Petazzoni
2014-06-06 7:15 ` Thomas Petazzoni
2014-06-06 16:14 ` Dallas Clement
2014-06-06 16:31 ` Mike Zick
2014-06-06 16:45 ` Dallas Clement
2014-06-10 9:32 ` Fabio Porcedda
2014-06-11 17:41 ` Dallas Clement
2014-06-13 9:23 ` Fabio Porcedda
2014-06-14 0:52 ` Dallas Clement
2014-06-14 7:57 ` Thomas Petazzoni [this message]
2014-06-18 12:37 ` Fabio Porcedda
2014-06-07 9:04 ` Thomas Petazzoni
2014-06-08 8:19 ` [Buildroot] [UNSURE]Re: " François Perrad
2014-06-09 20:10 ` Dallas Clement
2014-06-10 7:25 ` Thomas Petazzoni
2014-06-06 5:20 ` [Buildroot] " Waldemar Brodkorb
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=20140614095743.4b60810d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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