From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Parallel make messes up post-build in -next
Date: Thu, 20 Feb 2014 15:16:40 +0100 [thread overview]
Message-ID: <53060E48.2040403@mind.be> (raw)
In-Reply-To: <CAHkwnC-LRM1oVjxH1PNMHnB9x-H6C7QsO458t01TBtiFr2moOg@mail.gmail.com>
On 20/02/14 15:13, Fabio Porcedda wrote:
> On Thu, Feb 20, 2014 at 2:24 PM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> On Thu, Feb 20, 2014 at 10:55 AM, Eric Le Bihan
>> <eric.le.bihan.dev@free.fr> wrote:
>>> Hi!
>>>
>>> I am currently testing the -next branch and I've encountered the following
>>> problem: the copy of my overlay and the execution of my post-build script is
>>> now performed *after* the generation of my image.
>>>
>>> Reverting commit a24877586a566e052897e50e6a0c2f53cfb029f5, which adds support
>>> for top-level parallel make, fixes the issue.
>>>
>>> Has anyone else experienced this problem?
>>
>> I haven't tried it myself yet.
>> But, the rootfs and post build scripts are done from target-finalize,
>> and the rules to make the rootfs depend on target-finalize.
>> This should be fine (but probably is not and we're overlooking something).
>>
>> However, aside from the above I have another doubt: I don't see any
>> special handling for the other special targets like
>> target-purgelocales, target-generatelocales, ... These targets should
>> be run after all generic targets, and before creating the rootfs. As
>> far as I can see, they could now run in parallel with the normal
>> targets, right?
>
> Yes, it's a thing to fix for proper parallel bulding support, it's on
> my todo list.
>
> The targets target-finalize, target-purgelocales,
> target-generatelocales, toolchain-eclipse-register can be executed in
> parallel after building the generic targets?
I think target-finalize should depend on all other target-*. It's
something that you may want to call from the command line in order to get
an up-to-date target directory.
toolchain-eclipse-register can be done in parallel with all the rest, it
should just depend on toolchain. There is nothing really that depends on
it, so probably 'world' is the best choice.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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:[~2014-02-20 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 9:55 [Buildroot] Parallel make messes up post-build in -next Eric Le Bihan
2014-02-20 13:24 ` Thomas De Schampheleire
2014-02-20 14:13 ` Fabio Porcedda
2014-02-20 14:16 ` Arnout Vandecappelle [this message]
2014-02-20 14:28 ` Thomas De Schampheleire
2014-02-20 14:48 ` Arnout Vandecappelle
2014-02-20 15:04 ` Thomas De Schampheleire
2014-02-20 13:42 ` Fabio Porcedda
2014-02-20 14:00 ` Eric Le Bihan
2014-02-20 14:11 ` Fabio Porcedda
2014-02-20 14:00 ` Thomas De Schampheleire
2014-02-20 14:03 ` Thomas De Schampheleire
2014-02-20 14:15 ` Fabio Porcedda
2014-02-20 14:07 ` Fabio Porcedda
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=53060E48.2040403@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 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.