All of lore.kernel.org
 help / color / mirror / Atom feed
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:48:17 +0100	[thread overview]
Message-ID: <530615B1.1000205@mind.be> (raw)
In-Reply-To: <CAAXf6LWybp29EWQM6AsTPJ0r=PS1AYfU6ZmkYm3jEutxoZ8LEg@mail.gmail.com>

On 20/02/14 15:28, Thomas De Schampheleire wrote:
> Hi Fabio,
> 
> On Thu, Feb 20, 2014 at 3:13 PM, Fabio Porcedda
> <fabio.porcedda@gmail.com> wrote:
> [..]
>>
>> 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?
> 
> Since you can select both purgelocales and generatelocales, I would
> expect they need to be sequential: first purge then generate (as done
> today).

 True.

> I'd also expect that target-finalize should be finished before
> starting the locale stuff, as the post-build script or overlay may add
> additional locale stuff that needs to be purged.

 Hm, I would actually expect the reverse: whatever my post-build script
or overlay does should be final, and not be removed again by
purgelocales. But that is in fact not what happens at the moment.

 Regards,
 Arnout

> 
> Best regards,
> Thomas
> 


-- 
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

  reply	other threads:[~2014-02-20 14:48 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
2014-02-20 14:28     ` Thomas De Schampheleire
2014-02-20 14:48       ` Arnout Vandecappelle [this message]
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=530615B1.1000205@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.