Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] tvheadend: needs threads
Date: Thu, 23 May 2013 08:54:06 +0200	[thread overview]
Message-ID: <20130523065406.GC3373@free.fr> (raw)
In-Reply-To: <1369268647-13128-2-git-send-email-gilles.talis@gmail.com>

Gilles, All,

On 2013-05-22 17:24 -0700, Gilles Talis spake thusly:
> Signed-off-by: Gilles Talis <gilles.talis@gmail.com>
> ---
>  package/tvheadend/Config.in |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/package/tvheadend/Config.in b/package/tvheadend/Config.in
> index 19ab276..7083b01 100644
> --- a/package/tvheadend/Config.in
> +++ b/package/tvheadend/Config.in
> @@ -1,9 +1,10 @@
> -comment "tvheadend requires a toolchain with LARGEFILE and IPv6 support"
> -    depends on !BR2_LARGEFILE || !BR2_INET_IPV6
> +comment "tvheadend needs a toolchain with LARGEFILE, IPv6 and THREADS support"
> +    depends on !BR2_LARGEFILE || !BR2_INET_IPV6 || !BR2_TOOLCHAIN_HAS_THREADS
>  
>  config BR2_PACKAGE_TVHEADEND
>  	bool "tvheadend"
>  	depends on BR2_LARGEFILE && BR2_INET_IPV6
> +	depends on BR2_TOOLCHAIN_HAS_THREADS

Is it because tvheadend selects dvb-apps that it requires threads, or
does it itself require threads?

If the former, then:
	depends on BR2_TOOLCHAIN_HAS_THREADS # dvb-apps

If the latter, then OK.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-05-23  6:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  0:24 [Buildroot] [PATCH 1/5] dvb-apps utilities: needs threads Gilles Talis
2013-05-23  0:24 ` [Buildroot] [PATCH 2/5] tvheadend: " Gilles Talis
2013-05-23  6:54   ` Yann E. MORIN [this message]
2013-05-23 14:44     ` Gilles Talis
2013-05-23 17:42       ` Yann E. MORIN
2013-05-23 20:34   ` Peter Korsgaard
2013-05-23  0:24 ` [Buildroot] [PATCH 3/5] portaudio: " Gilles Talis
2013-05-23 20:37   ` Peter Korsgaard
2013-05-23  0:24 ` [Buildroot] [PATCH 4/5] portaudio: add license information Gilles Talis
2013-05-23  6:59   ` Yann E. MORIN
2013-05-23  7:09     ` Baruch Siach
2013-05-23  7:33       ` Yann E. MORIN
2013-05-23 14:49         ` Gilles Talis
2013-05-23 17:44           ` Yann E. MORIN
2013-05-23 17:52             ` Gilles Talis
2013-05-23  0:24 ` [Buildroot] [PATCH 5/5] libatomic_ops: fix build failure seen with toolchain without threads support Gilles Talis
2013-05-23 20:48   ` Peter Korsgaard
2013-05-23  6:51 ` [Buildroot] [PATCH 1/5] dvb-apps utilities: needs threads Yann E. MORIN
2013-05-23 20:33 ` 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=20130523065406.GC3373@free.fr \
    --to=yann.morin.1998@free.fr \
    --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