From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Parallel make messes up post-build in -next
Date: Thu, 20 Feb 2014 10:55:50 +0100 [thread overview]
Message-ID: <20140220095550.GA16493@pc-eric> (raw)
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?
Best regards,
ELB
next reply other threads:[~2014-02-20 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 9:55 Eric Le Bihan [this message]
2014-02-20 13:24 ` [Buildroot] Parallel make messes up post-build in -next 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
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=20140220095550.GA16493@pc-eric \
--to=eric.le.bihan.dev@free.fr \
--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.