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:55:13 +0100 [thread overview]
Message-ID: <20101106135513.58a13361@surf> (raw)
In-Reply-To: <871v6y39fj.fsf@macbook.be.48ers.dk>
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
next prev parent reply other threads:[~2010-11-06 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 12:44 [Buildroot] Results of random configuration builds Thomas Petazzoni
2010-11-06 12:48 ` Peter Korsgaard
2010-11-06 12:55 ` Thomas Petazzoni [this message]
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=20101106135513.58a13361@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