From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-19
Date: Mon, 20 Jul 2015 21:55:15 +0200 [thread overview]
Message-ID: <1437422115.1945.4.camel@embedded.rocks> (raw)
In-Reply-To: <20150720063017.2400B101C74@stock.ovh.net>
On Mo, 2015-07-20 at 08:30 +0200, Thomas Petazzoni wrote:
> Build statistics for 2015-07-19
> ===============================
>
> success : 230
> failures : 125
> timeouts : 6
> TOTAL : 361
>
> Classification of failures by reason
> ====================================
>
> arm | libtirpc-0.3.1 | NOK | http://autobuil
> d.buildroot.net/results/c537a76d17012821ed5a6f4170f759efd4d269b0/
> arm | libtirpc-0.3.1 | NOK |
> http://autobuild.buildroot.net/results/e3c5be7dca753f7494e8680894f516
> a8cdc89843/
> arm | libtirpc-0.3.1 | NOK | http://autobuil
> d.buildroot.net/results/2bb2e314f23b5ba48bb6e0c4fc7e52032fa5d76b/
> x86_64 | libtirpc-0.3.1 | NOK | http://autobuil
> d.buildroot.net/results/394073e0d85b56e6e470ff7a4be3f0f9fb592150/
All musl build errors. I am already working on this.
> arm | libtirpc-0.3.1 | NOK |
> http://autobuild.buildroot.net/results/80321de8d4c6c0a00439b07289a581
> 8962128b43/
This is odd:
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS is not set
# libtirpc needs a toolchain w/ threads
-> why is libtirpc build anyhow?
> arm | libtirpc-0.3.1 | NOK |
> http://autobuild.buildroot.net/results/51115754531fbb78b0e5f5bb6accf0
> 500cc6bf63/
>
next prev parent reply other threads:[~2015-07-20 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-19 Thomas Petazzoni
2015-07-20 12:30 ` Brendan Heading
2015-07-20 12:39 ` Thomas Petazzoni
2015-07-20 12:44 ` Baruch Siach
2015-07-20 12:49 ` Brendan Heading
2015-07-20 13:10 ` Thomas Petazzoni
2015-07-20 13:54 ` Brendan Heading
2015-07-20 19:55 ` Jörg Krause [this message]
2015-07-20 20:38 ` Thomas Petazzoni
2015-07-20 20:48 ` Jörg Krause
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=1437422115.1945.4.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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