From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Architecture build statistics
Date: Tue, 29 Oct 2013 21:16:22 +0100 [thread overview]
Message-ID: <20131029211622.62459eef@skate> (raw)
In-Reply-To: <52701682.2040208@zankel.net>
Dear Chris Zankel,
On Tue, 29 Oct 2013 13:11:46 -0700, Chris Zankel wrote:
> Great statistics. Xtensa definitely needs some work here ;-)
It seems yes :-)
Are you interested in receiving a daily e-mail with the Xtensa build
failures, if any?
> I looked into the failures a while ago and started to create patches.
Please submit them, then :)
> However, one major issue was lacking NPTL support in uClibc. We are
> currently working on it and are getting close to support it. This
> already should push the pct columns higher :-)
Unfortunately, seeing the absolute desert of release activity the
uClibc project is showing, I am not sure when any feature of this size
can be merged, and even worse released :-(
In the mean time, it would be good if we could identify such packages,
and add the appropriate dependencies to avoid autobuilder failures. Can
you point us which packages need NPTL support?
For the record, the 10 packages causing the highest number of problems
since July, 1st 2013, are:
+-------------------+-----+
| reason | cnt |
+-------------------+-----+
| binutils-2.21.1 | 96 |
| m4-1.4.16 | 37 |
| binutils-2.22 | 30 |
| libnspr-4.9.6 | 21 |
| m4-1.4.17 | 17 |
| cdrkit-1.1.11 | 14 |
| ffmpeg-0.8.12 | 8 |
| iozone-3_414 | 8 |
| gstreamer-0.10.36 | 6 |
| libpfm4-4.3.0 | 6 |
+-------------------+-----+
Looks like fixing binutils is a good thing to do in the very near
future. Can you send a patch for that?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-29 20:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 19:41 [Buildroot] Architecture build statistics Thomas Petazzoni
2013-10-29 20:11 ` Chris Zankel
2013-10-29 20:16 ` Thomas Petazzoni [this message]
2013-10-29 20:52 ` Chris Zankel
2013-10-29 21:36 ` Thomas Petazzoni
2013-10-30 6:00 ` Chris Zankel
2013-11-05 18:36 ` Chris Zankel
2013-10-29 21:24 ` Mischa Jonker
2013-10-29 21:28 ` Thomas Petazzoni
2013-10-29 22:02 ` Alvaro Gamez
2013-10-29 23:41 ` Ezequiel Garcia
2013-10-30 0:12 ` Thomas Petazzoni
2013-10-30 0:27 ` Ezequiel Garcia
2013-10-30 8:14 ` Christophe Vu-Brugier
2013-10-30 8:29 ` Thomas Petazzoni
2013-11-01 18:31 ` Thomas Petazzoni
2013-11-02 6:31 ` Sinan Akman
2013-11-02 10:05 ` Thomas Petazzoni
2013-11-02 16:00 ` Sinan Akman
2013-11-04 13:54 ` Matthew Weber
2013-11-02 15:16 ` Ezequiel García
2013-11-02 15:24 ` 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=20131029211622.62459eef@skate \
--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