From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] flac: update to version 1.3.0
Date: Wed, 04 Dec 2013 11:12:10 -0300 [thread overview]
Message-ID: <529F383A.1040407@zacarias.com.ar> (raw)
In-Reply-To: <1386150285.4433.2.camel@sven>
On 12/04/2013 06:44 AM, Sven Neumann wrote:
> On Di, 2013-12-03 at 19:40 -0300, Gustavo Zacarias wrote:
>> Hold off this one a bit, IIRC it failed miserably to run on MIPS and/or PPC.
>> Let me retry and see before comitting it.
>> Regards.
>
> Fine with me. I have only tested builds on two ARM platforms (XScale and
> Cortex-A8).
On qemu-mips-malta i get a floating point exception when encoding a
simple wav file (might be qemu at fault).
For powerpc altivec is still leaking inside leading to build failures
(or probably bad code) since it seems there are no powerpc processors
without altivec? 8-O
I'll concoct a patch for the altivec failure and test it, though i'd
need someone to test mips on real hardware.
Regards.
prev parent reply other threads:[~2013-12-04 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 22:11 [Buildroot] [PATCH] flac: update to version 1.3.0 Sven Neumann
2013-12-03 22:40 ` Gustavo Zacarias
2013-12-04 9:44 ` Sven Neumann
2013-12-04 14:12 ` Gustavo Zacarias [this message]
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=529F383A.1040407@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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