From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-02-22
Date: Mon, 23 Feb 2015 11:10:50 +0100 [thread overview]
Message-ID: <54EAFCAA.5070506@imgtec.com> (raw)
In-Reply-To: <20150223073016.4059D1027D4@stock.ovh.net>
Hello everyone,
On 23/02/15 08:30, Thomas Petazzoni wrote:
> Build statistics for 2015-02-22
> ===============================
>
> mips64el | openswan-2.6.42 | NOK | http://autobuild.buildroot.net/results/211d403c601ff73bd84b43881fb59fd7ee46389b/
I can't reproduce this, but I think it could be caused by a parallel
build issue. The same happened in mesa:
https://bugs.freedesktop.org/show_bug.cgi?id=83355
Regards,
--
Vincent
next prev parent reply other threads:[~2015-02-23 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-02-22 Thomas Petazzoni
2015-02-23 10:10 ` Vicente Olivert Riera [this message]
2015-02-23 11:23 ` Thomas Petazzoni
2015-02-23 12:34 ` Vicente Olivert Riera
2015-02-23 12:40 ` Thomas Petazzoni
2015-02-23 12:42 ` Vicente Olivert Riera
2015-02-23 12:14 ` Vicente Olivert Riera
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 22:57 Peter Seiderer
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=54EAFCAA.5070506@imgtec.com \
--to=vincent.riera@imgtec.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