From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-28
Date: Sun, 30 Mar 2014 17:27:03 +0200 [thread overview]
Message-ID: <20140330172703.4232fd90@skate> (raw)
In-Reply-To: <CAMo8BfKRHRtzpxNQpOyhpEf3EwxLL6ioRN+Kv0iSoSvkxWQDQA@mail.gmail.com>
Dear Max Filippov,
On Sat, 29 Mar 2014 21:06:40 +0400, Max Filippov wrote:
> On Sat, Mar 29, 2014 at 8:54 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> >> xtensa | mplayer-1.1.1 | NOK | http://autobuild.buildroot.net/results/db06965d3984ab6ca5e039f0e35d4be8638c488b/
> >
> > Baruch, this is a Xtensa specific failure, can you have a look ?
>
> A fix for this and other similar issue with wireshark was posted last sunday:
> http://comments.gmane.org/gmane.comp.lib.uclibc.buildroot/80105
>
> For this fix to be complete we need the following patch to be merged to uclibc:
> http://permalink.gmane.org/gmane.comp.lib.uclibc.general/23828
Can you send a Buildroot patch that adds this uClibc patch to the
Xtensa version? This way, I could test that both of the patches
combined solve the wireshark and mplayer problems.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-30 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-28 Thomas Petazzoni
2014-03-29 16:54 ` Thomas Petazzoni
2014-03-29 17:06 ` Max Filippov
2014-03-30 15:27 ` Thomas Petazzoni [this message]
2014-03-30 22:09 ` Marcelo Gutierrez
2014-03-29 19:16 ` Gustavo Zacarias
2014-03-30 5:11 ` Baruch Siach
2014-04-03 13:13 ` Baruch Siach
2014-03-30 11:59 ` Yegor Yefremov
2014-04-05 12:48 ` Thomas Petazzoni
2014-04-05 14:44 ` Yegor Yefremov
2014-04-05 17:07 ` Thomas Petazzoni
2014-03-31 10:24 ` Anton Kolesov
2014-03-31 10:32 ` Thomas Petazzoni
2014-03-31 10:42 ` Anton Kolesov
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=20140330172703.4232fd90@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.