From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] Fix for top-level parallel make part 1
Date: Tue, 30 Jul 2013 12:01:57 +0200 [thread overview]
Message-ID: <20130730120157.0d32a58b@skate> (raw)
In-Reply-To: <CAHkwnC-yTeGXQnh64-Ra_TJg4ysYqAPNsNaWhA=_sgiUm5R5bw@mail.gmail.com>
Dear Fabio Porcedda,
On Tue, 30 Jul 2013 11:34:08 +0200, Fabio Porcedda wrote:
> > As per OpenEmbedded/Bitbake, I was told a few years ago that they were
> > not doing per-package sysroot, even though they are doing top-level
> > parallel builds, and that this was sometimes causing some spurious
> > failures or not completely reproducible builds. However, I haven't
> > verified this myself, and this statement was made some years ago, so it
> > may or may not longer be true.
>
> Unfortunately right now i've not enough time to work on the
> per-package sysroot feature, maybe in the feature, i don't know.
>
> So are you going to accept this patch set even without per-package
> sysroot feature?
> IMHO top-level parallel make it's still a useful feature even without
> per-package sysroot.
> The per-package sysroot feature can be still added later.
As we discussed in this thread, the problem is that the top-level
parallel make feature is broken if you don't have per-package sysroot:
builds become non-reproducible.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-30 10:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 9:12 [Buildroot] [PATCH v2 0/3] Fix for top-level parallel make part 1 Fabio Porcedda
2013-07-18 9:12 ` [Buildroot] [PATCH v2 1/3] package/Makefile.in: add a way to don't force jobs in sub-make Fabio Porcedda
2013-08-21 19:17 ` Arnout Vandecappelle
2013-07-18 9:12 ` [Buildroot] [PATCH v2 2/3] package: fix generic extract target for top-level parallel make Fabio Porcedda
2013-08-21 19:24 ` Arnout Vandecappelle
2013-08-22 7:44 ` Fabio Porcedda
2013-08-22 15:59 ` Arnout Vandecappelle
2013-08-23 11:31 ` Fabio Porcedda
2013-08-26 8:29 ` Fabio Porcedda
2013-08-27 6:01 ` Arnout Vandecappelle
2013-08-28 8:26 ` Fabio Porcedda
2013-08-23 7:36 ` Thomas Petazzoni
2013-08-23 8:00 ` Fabio Porcedda
2013-08-23 11:14 ` Thomas Petazzoni
2013-07-18 9:12 ` [Buildroot] [PATCH v2 3/3] package: fix generic patch " Fabio Porcedda
2013-07-18 9:38 ` [Buildroot] [PATCH v2 0/3] Fix for top-level parallel make part 1 Thomas Petazzoni
2013-07-19 15:41 ` Fabio Porcedda
2013-07-27 11:18 ` Thomas Petazzoni
2013-07-30 9:34 ` Fabio Porcedda
2013-07-30 10:01 ` Thomas Petazzoni [this message]
2013-07-30 10:16 ` Fabio Porcedda
2013-07-30 11:29 ` Thomas Petazzoni
2013-08-12 16:48 ` Arnout Vandecappelle
2013-08-20 12:14 ` Fabio Porcedda
2013-08-20 17:35 ` Arnout Vandecappelle
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=20130730120157.0d32a58b@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