[Buildroot] Results of random configuration builds

[Buildroot] Results of random configuration builds

[Thomas Petazzoni]

Hello,

I've run a few random build tests yesterday, and analyzed the results a
bit today. I've set up a small webpage that gathers the results,
together with the logfile and the configuration for each test.

See http://free-electrons.com/~thomas/pub/buildroot-logs/

Most of the builds are failing. The worst problem is that libglib2 does
not build in many situations (see
http://free-electrons.com/~thomas/pub/buildroot-logs/test-195/logfile-end).
There are also problems with logrotate, gvfs, libgcrypt, olsr, libmad,
netperf, magiccube4d, libmpeg2, xfsprogs, imagemagick, squid, ltrace,
tcpdump, bash, gmp, gdb.

It'd be great if some of the readers of this list could have a look at
one or several of these build problems, so that we can collaboratively
solve them.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Results of random configuration builds

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Hello,
 Thomas> I've run a few random build tests yesterday, and analyzed the results a
 Thomas> bit today. I've set up a small webpage that gathers the results,
 Thomas> together with the logfile and the configuration for each test.

 Thomas> See http://free-electrons.com/~thomas/pub/buildroot-logs/

Thanks, I also have a bunch of build logs on gcc10.fsffrance.org

 Thomas> Most of the builds are failing. The worst problem is that libglib2 does
 Thomas> not build in many situations (see
 Thomas> http://free-electrons.com/~thomas/pub/buildroot-logs/test-195/logfile-end).
 Thomas> There are also problems with logrotate, gvfs, libgcrypt, olsr, libmad,
 Thomas> netperf, magiccube4d, libmpeg2, xfsprogs, imagemagick, squid, ltrace,
 Thomas> tcpdump, bash, gmp, gdb.

 Thomas> It'd be great if some of the readers of this list could have a look at
 Thomas> one or several of these build problems, so that we can collaboratively
 Thomas> solve them.

I've noticed the tcpdump issue as well, and I'm fixing that now.

-- 
Bye, Peter Korsgaard

[Buildroot] Results of random configuration builds

[Thomas Petazzoni]

On Sat, 06 Nov 2010 13:48:00 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:

> Thanks, I also have a bunch of build logs on gcc10.fsffrance.org

Are they publicly available / visible ?

> I've noticed the tcpdump issue as well, and I'm fixing that now.

Thanks, I've updated
http://free-electrons.com/~thomas/pub/buildroot-logs/ accordingly.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Results of random configuration builds

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> On Sat, 06 Nov 2010 13:48:00 +0100
 Thomas> Peter Korsgaard <jacmet@uclibc.org> wrote:

 >> Thanks, I also have a bunch of build logs on gcc10.fsffrance.org

 Thomas> Are they publicly available / visible ?

Sorry, so far only if you have a login to the gcc cluster
(~peko/logs). Could you share your web scripts so I can put something
online?

 >> I've noticed the tcpdump issue as well, and I'm fixing that now.

 Thomas> Thanks, I've updated
 Thomas> http://free-electrons.com/~thomas/pub/buildroot-logs/ accordingly.

I also fixed the tslib issue yesterday.

-- 
Bye, Peter Korsgaard

[Buildroot] Results of random configuration builds

[Lionel Landwerlin]

Le samedi 06 novembre 2010 ? 13:59 +0100, Peter Korsgaard a ?crit :
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

> 
> I also fixed the tslib issue yesterday.
> 

I posted a patch for the directfb issue on sqrt yesterday too.

[Buildroot] Results of random configuration builds

[Lionel Landwerlin]

Thomas,

It seems you've strange toolchains :)
It seems the glib breakage is due to a compiler not supporting builtin
atomic operations, which is strange for x86.
I'm not able to reproduce with internal or external glibc/sh4
toolchains.

Can test with the attached patch to apply on glib2 ?

Regards,

--
Lionel Landwerlin

Le samedi 06 novembre 2010 ? 13:44 +0100, Thomas Petazzoni a ?crit :
> Hello,
> 
> I've run a few random build tests yesterday, and analyzed the results a
> bit today. I've set up a small webpage that gathers the results,
> together with the logfile and the configuration for each test.
> 
> See http://free-electrons.com/~thomas/pub/buildroot-logs/
> 
> Most of the builds are failing. The worst problem is that libglib2 does
> not build in many situations (see
> http://free-electrons.com/~thomas/pub/buildroot-logs/test-195/logfile-end).
> There are also problems with logrotate, gvfs, libgcrypt, olsr, libmad,
> netperf, magiccube4d, libmpeg2, xfsprogs, imagemagick, squid, ltrace,
> tcpdump, bash, gmp, gdb.
> 
> It'd be great if some of the readers of this list could have a look at
> one or several of these build problems, so that we can collaboratively
> solve them.
> 
> Thanks!
> 
> Thomas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-glib-fix-compilation-with-no-builtin-atomic-operatio.patch
Type: text/x-patch
Size: 797 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101106/dd5ae904/attachment.bin>

[Buildroot] Results of random configuration builds

[Thomas Petazzoni]

Hello,

On Sat, 06 Nov 2010 15:05:42 +0100
Lionel Landwerlin <llandwerlin@gmail.com> wrote:

> It seems you've strange toolchains :)
> It seems the glib breakage is due to a compiler not supporting builtin
> atomic operations, which is strange for x86.
> I'm not able to reproduce with internal or external glibc/sh4
> toolchains.

I was building for i386, and on i386 the
__sync_bool_compare_and_swap_4() is not available.

> Can test with the attached patch to apply on glib2 ?

I confirm it fixes the problem on i386 toolchains. I haven't tested
with my sh4 toolchain, but since the problem is the same, I suspect it
also fixed the problem.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Results of random configuration builds

[Lionel Landwerlin]

Le samedi 06 novembre 2010 ? 17:06 +0100, Thomas Petazzoni a ?crit :
> Hello,
> 
> On Sat, 06 Nov 2010 15:05:42 +0100
> Lionel Landwerlin <llandwerlin@gmail.com> wrote:
> 
> > It seems you've strange toolchains :)
> > It seems the glib breakage is due to a compiler not supporting builtin
> > atomic operations, which is strange for x86.
> > I'm not able to reproduce with internal or external glibc/sh4
> > toolchains.
> 
> I was building for i386, and on i386 the
> __sync_bool_compare_and_swap_4() is not available.
> 
> > Can test with the attached patch to apply on glib2 ?
> 
> I confirm it fixes the problem on i386 toolchains. I haven't tested
> with my sh4 toolchain, but since the problem is the same, I suspect it
> also fixed the problem.
> 
> Thanks!

I just found it has been reported on the glib bugzilla :

https://bugzilla.gnome.org/show_bug.cgi?id=631353

Regards,

--
Lionel Landwerlin

[Buildroot] Results of random configuration builds

[Will Newton]

On Sat, Nov 6, 2010 at 12:44 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> I've run a few random build tests yesterday, and analyzed the results a
> bit today. I've set up a small webpage that gathers the results,
> together with the logfile and the configuration for each test.
>
> See http://free-electrons.com/~thomas/pub/buildroot-logs/
>
> Most of the builds are failing. The worst problem is that libglib2 does
> not build in many situations (see
> http://free-electrons.com/~thomas/pub/buildroot-logs/test-195/logfile-end).
> There are also problems with logrotate, gvfs, libgcrypt, olsr, libmad,
> netperf, magiccube4d, libmpeg2, xfsprogs, imagemagick, squid, ltrace,
> tcpdump, bash, gmp, gdb.

I've noticed ltrace breaks quite frequently because it is built from
the debian archive, which doesn't guarantee that the package will
remain available forever. I wonder whether we should be building
anything from the debian archive directly and build from
archive.debian.net instead.

[Buildroot] Results of random configuration builds

[Peter Korsgaard]

>>>>> "Will" == Will Newton <will.newton@gmail.com> writes:

Hi,

 Will> I've noticed ltrace breaks quite frequently because it is built from
 Will> the debian archive, which doesn't guarantee that the package will
 Will> remain available forever. I wonder whether we should be building
 Will> anything from the debian archive directly and build from
 Will> archive.debian.net instead.

The archive is normally preferred, but a missing upstream shouldn't
matter much with the backup mirror (sources.buildroot.net). Is that
somehow not working for you?

-- 
Bye, Peter Korsgaard

[Buildroot] Results of random configuration builds

[Will Newton]

On Sat, Nov 6, 2010 at 4:11 PM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Will" == Will Newton <will.newton@gmail.com> writes:
>
> Hi,
>
> ?Will> I've noticed ltrace breaks quite frequently because it is built from
> ?Will> the debian archive, which doesn't guarantee that the package will
> ?Will> remain available forever. I wonder whether we should be building
> ?Will> anything from the debian archive directly and build from
> ?Will> archive.debian.net instead.
>
> The archive is normally preferred, but a missing upstream shouldn't
> matter much with the backup mirror (sources.buildroot.net). Is that
> somehow not working for you?

I just tested it and it works for me now (i386), so I'm not sure what
the problem was that I saw previously.