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 15:00:11 +0100 [thread overview]
Message-ID: <20140220140010.GB16493@pc-eric> (raw)
In-Reply-To: <CAHkwnC-Pm8qE8beKmaJKkHsioOuGjWrgcM8oyxni2AuDChYF+Q@mail.gmail.com>
Hi!
On Thu, Feb 20, 2014 at 02:42:17PM +0100, Fabio Porcedda 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?
> >
>
> Can you try this patch?
>
> diff --git a/Makefile b/Makefile
> index 20aabd6..de568e3 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -507,6 +507,8 @@ endif
> STRIP_FIND_CMD += -type f \( -perm /111 -o -name '*.so*' \)
> STRIP_FIND_CMD += -not \( $(call findfileclauses,libpthread*.so*
> $(call qstrip,$(BR2_STRIP_EXCLUDE_FILES))) \) -print
>
> +$(TARGETS_ROOTFS): target-finalize
> +
> target-finalize: $(TARGETS)
> rm -rf $(TARGET_DIR)/usr/include $(TARGET_DIR)/usr/share/aclocal \
> $(TARGET_DIR)/usr/lib/pkgconfig
> $(TARGET_DIR)/usr/share/pkgconfig \
> @@ -534,8 +536,6 @@ endif
> find $(TARGET_DIR)/lib/modules -type f -name '*.ko' | \
> xargs -r $(KSTRIPCMD); fi
>
> -$(TARGETS_ROOTFS): target-finalize
> -
> # See http://sourceware.org/gdb/wiki/FAQ, "GDB does not see any threads
> # besides the one in which crash occurred; or SIGTRAP kills my program when
> # I set a breakpoint"
The patch fixes the issue. Thank you very much!
Best regards,
ELB
next prev parent reply other threads:[~2014-02-20 14:00 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
2014-02-20 15:04 ` Thomas De Schampheleire
2014-02-20 13:42 ` Fabio Porcedda
2014-02-20 14:00 ` Eric Le Bihan [this message]
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=20140220140010.GB16493@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox