From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] package/pulseaudio: fix musl build
Date: Thu, 6 Aug 2015 09:04:25 +0200 [thread overview]
Message-ID: <20150806090425.1917eff0@free-electrons.com> (raw)
In-Reply-To: <1438370022-25257-1-git-send-email-romain.naour@openwide.fr>
Dear Romain Naour,
On Fri, 31 Jul 2015 21:13:42 +0200, Romain Naour wrote:
> pulseaudio doesn't build properly on musl due to
> a OSS wrapper called padsp. It provide a software OSS
> interface on systems without OSS.
>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> Patches not upstreamed yet.
Could you send your patches upstream, and see what is upstream
reaction? That's quite a bit of patches, to support a fairly odd setup
(a big thing such as pulseaudio, with a small size C library such as
musl). So I'd prefer to have such patches upstreamed.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-06 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 19:13 [Buildroot] [RFC] package/pulseaudio: fix musl build Romain Naour
2015-08-06 7:04 ` Thomas Petazzoni [this message]
2015-08-06 8:35 ` Romain Naour
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=20150806090425.1917eff0@free-electrons.com \
--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