From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] Architecture build statistics
Date: Tue, 05 Nov 2013 10:36:48 -0800 [thread overview]
Message-ID: <52793AC0.4090306@zankel.net> (raw)
In-Reply-To: <20131029211622.62459eef@skate>
Hi Thomas,
Just a quick update on binutils. There seems to be an issue with uClibc
(_obstack_* symbols are not exported). I also tried a similar build for
ARM with the same result (same error). Do you have any test builds using
a uClibc snapshot for other architectures that pass binutils?
There was a discussion about it on the uClibc mailing list a while ago.
Thanks,
-Chris
On 10/29/13, 1:16 PM, Thomas Petazzoni wrote:
> 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?
next prev parent reply other threads:[~2013-11-05 18:36 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
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 [this message]
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=52793AC0.4090306@zankel.net \
--to=chris@zankel.net \
--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