From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and top-level parallel make
Date: Sat, 14 Jul 2012 23:37:48 +0200 [thread overview]
Message-ID: <5001E6AC.2040501@mind.be> (raw)
In-Reply-To: <CA+wH297K1Fh6cgFaHo2dd=ihgujo_nMkyicJLnOvAm9jnonBcQ@mail.gmail.com>
On 07/13/12 12:34, Alex Bradbury wrote:
> On 4 July 2012 13:20, Alex Bradbury<asb@asbradbury.org> wrote:
>> > On 28 June 2012 13:34, Alex Bradbury<asb@asbradbury.org> wrote:
>>> >> I was wondering what the outcome of experiments to allow top-level
>>> >> parallelism were? What are the major barriers to allowing this? Is it
>>> >> still something seen as feasible to add to buildroot, or is it looking
>>> >> like it would add too much complexity?
>> >
>> > Thomas, I was wondering if you'd been able to recall what issues your
>> > initial experiments with top-level parallel make faced?
> I hate to be a pain...but ping?
I guess Thomas doesn't remember :-)
I believe the main problem is in the non-package targets, e.g.
target-generic-hostname. They are just added to TARGETS without
further dependencies. Same is true for the toolchain: it is just
prepended to TARGETS.
Changing that requires careful thinking about how the TARGETS work,
and is not easy to verify because there are a lot of corner cases involved.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-07-14 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 12:34 [Buildroot] Buildroot and top-level parallel make Alex Bradbury
2012-06-30 12:48 ` Arnout Vandecappelle
2012-06-30 22:22 ` Alex Bradbury
2012-07-04 12:20 ` Alex Bradbury
2012-07-13 10:34 ` Alex Bradbury
2012-07-14 21:37 ` Arnout Vandecappelle [this message]
2012-07-15 20:16 ` 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=5001E6AC.2040501@mind.be \
--to=arnout@mind.be \
--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