From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Antw: build speedup possible?
Date: Fri, 7 Feb 2014 16:29:34 +0100 [thread overview]
Message-ID: <20140207162934.01acfe5a@skate> (raw)
In-Reply-To: <CAHkwnC_B8RRAXBOGjjpr2X7CbZpVTnsDx8QoLEPfaieEoSd4gA@mail.gmail.com>
Dear Fabio Porcedda,
On Fri, 7 Feb 2014 15:48:35 +0100, Fabio Porcedda wrote:
> The build can be reproduced even when building packages in parallel,
> we just need to record the order of the steps and replay that order if
> needed.
And in practice, how do you achieve this? When building in parallel,
how do you record the fact that the test for libfoo in package A
configure script was run before or after the installation of libfoo in
the global sysroot? It's not only about recording the order of the
build of the package: it's knowing whether each specific test of a
configure script was run before or after the corresponding library was
installed in the global sysroot.
> The sysroot copy is needed only to be sure that even if some package
> has an unspecified optional dependency it generates every time the
> same binary.
Which is *the* very important thing. So saying it's needed "only to be
sure" is quite minimizing the very important consequence of parallel
build with a global sysroot, IMO.
> I think that at least when doing development it will be useful to
> build packages in parallel.
> Maybe it will be best to avoid building packages in parallel just for releases.
I don't agree.
I do a lot of support on #buildroot, and I would *hate* to have people
coming up with bug reports that are not reproducible because they
depend on the specific scheduling of the build. I really don't want new
comers to use this feature and then come back with bug reports that are
basically unfixable because they cannot be reproduced.
I think we should really not minimize the support problem that
parallelization without per-package sysroot is going to cause.
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-02-07 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:51 [Buildroot] build speedup possible? Andreas Naumann
2014-02-07 8:54 ` Maxime Hadjinlian
2014-02-07 9:00 ` [Buildroot] Antw: " Frank Ihle
2014-02-07 10:31 ` Samuel Martin
2014-02-07 13:35 ` Andreas Naumann
2014-02-07 15:17 ` Fabio Porcedda
2014-02-07 14:48 ` Fabio Porcedda
2014-02-07 15:03 ` Fabio Porcedda
2014-02-07 15:29 ` Thomas Petazzoni [this message]
2014-02-07 15:54 ` Fabio Porcedda
2014-02-07 16:43 ` Thomas Petazzoni
2014-02-07 18:05 ` Fabio Porcedda
2014-02-10 8:38 ` Thomas Petazzoni
2014-02-10 11:31 ` Andreas Naumann
2014-02-10 12:15 ` Thomas Petazzoni
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=20140207162934.01acfe5a@skate \
--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 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.