From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] sox: new package
Date: Tue, 01 Jul 2014 09:52:47 -0300 [thread overview]
Message-ID: <53B2AF1F.9060602@zacarias.com.ar> (raw)
In-Reply-To: <87tx71gs2d.fsf@dell.be.48ers.dk>
On 07/01/2014 09:51 AM, Peter Korsgaard wrote:
> Any specific reason to unconditionally disable ffmpeg support?
Yes, it uses old API calls that aren't supported with our current version.
Regards.
next prev parent reply other threads:[~2014-07-01 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 1:38 [Buildroot] [PATCH 1/3] twolame: new package Gustavo Zacarias
2014-06-28 1:38 ` [Buildroot] [PATCH 2/3] opencore-amr: " Gustavo Zacarias
2014-06-28 1:38 ` [Buildroot] [PATCH 3/3] sox: " Gustavo Zacarias
2014-07-01 12:51 ` Peter Korsgaard
2014-07-01 12:52 ` Gustavo Zacarias [this message]
2014-07-01 13:02 ` Peter Korsgaard
2014-07-01 12:51 ` [Buildroot] [PATCH 1/3] twolame: " Peter Korsgaard
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=53B2AF1F.9060602@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