From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dmalloc: fix parallel builds
Date: Sun, 4 Jan 2015 21:02:04 +0200 [thread overview]
Message-ID: <20150104190204.GA4224@vostro> (raw)
In-Reply-To: <20150104183513.0cdff028@free-electrons.com>
Sun, Jan 04, 2015 at 06:35:13PM +0100, Thomas Petazzoni wrote:
> On Sat, 3 Jan 2015 13:05:03 +0200, Alex Suykov wrote:
> > Signed-off-by: Alex Suykov <alex.suykov@gmail.com>
> > ---
> > This patch should fix
> > http://autobuild.buildroot.net/results/2cc40ae3fc8b7a287c43528b3e4ffdbcd5033c09/
> >
> > package/dmalloc/dmalloc-deps.patch | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> > create mode 100644 package/dmalloc/dmalloc-deps.patch
>
> While it indeed looks like a parallel build issue, I haven't been able
> to reproduce it: I've started a loop building dmalloc over and over
> again on my build server (on which the issue was reproduced by the
> autobuilders), and never managed to see it after an entire night
> looping on dmalloc builds. So I'm a bit confused on this one.
The following sequence seems to trigger it more or less reliably for me:
./configure --disable-static --enable-shared --enable-cxx --enable-threads
sed -i -e "s at cat \$(srcdir)/dmalloc.h.1.*@&; sleep 1@" Makefile
make clean
make -j4
What happens is a race condition between "cat ...; mv ... dmalloc.h"
and "g++ -c dmallocc.cc". As long as cat-mv pair is faster, it works well.
But if there's a delay, it breaks.
This should be rare, I can only reproduce it with an artificial delay,
and only with --disable-static. But on the other hand, it did happen
on autobuild somehow.
next prev parent reply other threads:[~2015-01-04 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 11:05 [Buildroot] [PATCH] dmalloc: fix parallel builds Alex Suykov
2015-01-04 17:35 ` Thomas Petazzoni
2015-01-04 19:02 ` Alex Suykov [this message]
2015-01-04 20:41 ` Thomas Petazzoni
2015-01-07 13:02 ` Alex Suykov
2015-01-07 13:17 ` 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=20150104190204.GA4224@vostro \
--to=alex.suykov@gmail.com \
--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