Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Antw: build speedup possible?
Date: Fri, 7 Feb 2014 17:43:55 +0100	[thread overview]
Message-ID: <20140207174355.383b6bb3@skate> (raw)
In-Reply-To: <CAHkwnC-pAGs0DCu80X3_AQgrsxcOO82GMY7NwmegxT6V0_kwJw@mail.gmail.com>

Dear Fabio Porcedda,

On Fri, 7 Feb 2014 16:54:20 +0100, Fabio Porcedda wrote:

> > 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.
> 
> Well i admit i haven't thought about that corner case, I don't know an
> easy solution for that.

IMO this is not a corner case, this is precisely the problem we have
been pointing out since the beginning when mixing a global sysroot with
top-level parallelization.

> > I think we should really not minimize the support problem that
> > parallelization without per-package sysroot is going to cause.
> 
> My suggestion was based on the assumption that there is a way to
> reproduce the exact build order.
> But if that is not true i agree with you.

I don't really see how to reproduce the exact build order, so the
support problem will be here. That's really why I have been a bit
skeptical and resistant to this patch series from the very beginning. I
am obviously very interested in ways to reduce the build time. But
doing that at the expense of reliability is not a good idea in my
opinion, as users will face spurious failures that we will not be able
to reproduce and fix.

If we want to get this to the next level, someone need to experiment
with per-package sysroot. Of course, this would be a long experiment,
without necessarily at the end the guarantee that we will accept it,
because it may be too complex to match Buildroot simplicity principle.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-02-07 16:43 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
2014-02-07 15:54         ` Fabio Porcedda
2014-02-07 16:43           ` Thomas Petazzoni [this message]
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=20140207174355.383b6bb3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox