Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtirpc: needs threads
Date: Thu, 12 Sep 2013 20:23:28 +0200	[thread overview]
Message-ID: <20130912202328.67b9aca1@skate> (raw)
In-Reply-To: <1378539885.24773.0.camel@phoenix>

Dear Axel Lin,

On Sat, 07 Sep 2013 15:44:45 +0800, Axel Lin wrote:
> Fixes:
> http://autobuild.buildroot.net/results/250/25008a6f0a854e1e29a3340536eef817eeb5752e/
> 
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
>  package/libtirpc/Config.in | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/libtirpc/Config.in b/package/libtirpc/Config.in
> index b9db5aa..a2dadce 100644
> --- a/package/libtirpc/Config.in
> +++ b/package/libtirpc/Config.in
> @@ -7,6 +7,7 @@ config BR2_PACKAGE_LIBTIRPC
>  	# used instead of libtirpc.
>  	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 && \
>  		!BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1
> +	depends on BR2_TOOLCHAIN_HAS_THREADS
>  	help
>  	  Libtirpc is a port of Sun's Transport-Independent RPC
>  	  library to Linux.

This doesn't work because there are packages that select
BR2_PACKAGE_LIBTIRPC, so the thread dependency should be propagated to
those packages.

Samuel already submitted such a patch a while ago
(http://patchwork.ozlabs.org/patch/244409/). It'd be good to refresh it
and resend.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-09-12 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07  7:44 [Buildroot] [PATCH] libtirpc: needs threads Axel Lin
2013-09-12 18:23 ` 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=20130912202328.67b9aca1@skate \
    --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