From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-09-07
Date: Tue, 8 Sep 2015 16:06:51 +0200 [thread overview]
Message-ID: <20150908160651.175c9846@free-electrons.com> (raw)
In-Reply-To: <55EEEACA.6020202@imgtec.com>
Vicente,
On Tue, 8 Sep 2015 15:03:54 +0100, Vicente Olivert Riera wrote:
> On 09/08/2015 07:30 AM, Thomas Petazzoni wrote:
> > Build statistics for 2015-09-07
>
> > mips64el | setools-3.3.8 | NOK | http://autobuild.buildroot.net/results/1196ac448c77320b59b63b6133d2d1af1245bf69/
>
> This is a race condition and I have reported it upstream:
>
> https://github.com/TresysTechnology/setools3/issues/5
>
> Should we build setools with -j1 until upstream fixes the problem?
Yes, if you verified that building with -j1 fixed the problem, then
yes, we should use it for the moment.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-09-08 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-09-07 Thomas Petazzoni
2015-09-08 14:03 ` Vicente Olivert Riera
2015-09-08 14:06 ` Thomas Petazzoni [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=20150908160651.175c9846@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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