From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] poco: avoid build failures on multicore hosts
Date: Fri, 20 Jan 2017 21:19:42 +0100 [thread overview]
Message-ID: <87wpdpqyap.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1484936334-19116-1-git-send-email-casantos@datacom.ind.br> (Carlos Santos's message of "Fri, 20 Jan 2017 16:18:54 -0200")
>>>>> "Carlos" == Carlos Santos <casantos@datacom.ind.br> writes:
> Parallel build still fails on heavilly multicore machines (e.g. -j25)
> and hacks likecommit 32f4957b153bdabe7af60d529942aca7d1a4783d do not
> seem to be effective.
> Let's simply use MAKE1 for the build step, instead.
> Fixes:
> http://autobuild.buildroot.net/results/388/38834ad3013fe79e5e4f75997133f1bd827be6dc
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> Extra information: here at DATACOM we have a build farm with several
> multicore blades that usually build with "make -j25". With this setup we
> have been observing compilation failures each two days.
> Change-Id: If80cd0b01ceb8b0aee886ea96a266fa864fa8eb0
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-01-20 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 18:18 [Buildroot] [PATCH] poco: avoid build failures on multicore hosts Carlos Santos
2017-01-20 20:19 ` Peter Korsgaard [this message]
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=87wpdpqyap.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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