Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Results of random configuration builds
Date: Sat, 6 Nov 2010 13:44:54 +0100	[thread overview]
Message-ID: <20101106134454.7769d258@surf> (raw)

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

             reply	other threads:[~2010-11-06 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06 12:44 Thomas Petazzoni [this message]
2010-11-06 12:48 ` [Buildroot] Results of random configuration builds Peter Korsgaard
2010-11-06 12:55   ` Thomas Petazzoni
2010-11-06 12:59     ` Peter Korsgaard
2010-11-06 13:03       ` Lionel Landwerlin
2010-11-06 14:05 ` Lionel Landwerlin
2010-11-06 16:06   ` Thomas Petazzoni
2010-11-06 16:44     ` Lionel Landwerlin
2010-11-06 15:07 ` Will Newton
2010-11-06 16:11   ` Peter Korsgaard
2010-11-06 16:24     ` Will Newton

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=20101106134454.7769d258@surf \
    --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