From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] shairport-sync: needs toolchain with NPTL
Date: Thu, 30 Oct 2014 21:52:48 +0100 [thread overview]
Message-ID: <20141030215248.4afed119@free-electrons.com> (raw)
In-Reply-To: <4f23aeb270143c08f76b81f8ff30c76ea8407a4b.1414589620.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Wed, 29 Oct 2014 15:33:40 +0200, Baruch Siach wrote:
> Also remove the comment attributing threads dependency to alsa-lib, since
> shairport-sync itself uses pthreads.
>
> Fixes:
> http://autobuild.buildroot.net/results/58e/58eafd2499919a45bfb5a2becc233d3678deedde/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/shairport-sync/Config.in | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied, thanks. And thanks to Arnout for the review.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-30 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 13:33 [Buildroot] [PATCH] shairport-sync: needs toolchain with NPTL Baruch Siach
2014-10-30 8:20 ` Arnout Vandecappelle
2014-10-30 20:52 ` Thomas Petazzoni [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=20141030215248.4afed119@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