From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] libnfs: Without native RPC use libtirpc
Date: Sat, 3 Oct 2015 19:22:40 +0100 [thread overview]
Message-ID: <56101CF0.2070006@mind.be> (raw)
In-Reply-To: <1443890749-27092-3-git-send-email-maxime.hadjinlian@gmail.com>
On 03-10-15 17:45, Maxime Hadjinlian wrote:
> Signed-off-by Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> v1 -> v2:
> - Don't depends on blackfin toolchain (is removed by previous
> patch)
> ---
> package/libnfs/Config.in | 7 ++++---
> package/libnfs/libnfs.mk | 4 ++++
> 2 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/package/libnfs/Config.in b/package/libnfs/Config.in
> index 6642fe4..2a1ef03 100644
> --- a/package/libnfs/Config.in
> +++ b/package/libnfs/Config.in
> @@ -1,10 +1,11 @@
> config BR2_PACKAGE_LIBNFS
> bool "libnfs"
> - depends on BR2_TOOLCHAIN_HAS_NATIVE_RPC
> + depends on BR2_TOOLCHAIN_HAS_NATIVE_RPC || BR2_TOOLCHAIN_HAS_THREADS # libtirpc
> + select BR2_PACKAGE_LIBTIRPC if !BR2_TOOLCHAIN_HAS_NATIVE_RPC
> help
> nfs userspace implementation.
>
> http://github.com/sahlberg/libnfs
>
> -comment "libnfs needs a toolchain w/ RPC"
> - depends on !BR2_TOOLCHAIN_HAS_NATIVE_RPC
> +comment "libnfs needs a toolchain w/ threads"
> + depends on !(BR2_TOOLCHAIN_HAS_THREADS || BR2_TOOLCHAIN_HAS_NATIVE_RPC)
> diff --git a/package/libnfs/libnfs.mk b/package/libnfs/libnfs.mk
> index 0c8c4f5..fb95e21 100644
> --- a/package/libnfs/libnfs.mk
> +++ b/package/libnfs/libnfs.mk
> @@ -13,4 +13,8 @@ LIBNFS_LICENSE = LGPLv2.1+
> LIBNFS_LICENSE_FILES = LICENCE-LGPL-2.1.txt
> LIBNFS_DEPENDENCIES = host-pkgconf
>
> +ifeq ($(BR2_PACKAGE_LIBTIRPC),y)
> +LIBNFS_DEPENDENCIES += libtirpc
> +endif
> +
> $(eval $(autotools-package))
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-03 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 16:45 [Buildroot] [PATCH 1/4] toolchain-external: Remove BLACKFIN_UCLINUX_2012R2 Maxime Hadjinlian
2015-10-03 16:45 ` [Buildroot] [PATCH 2/4] blackfin: 2012R2 toolchain is gone, remove kludges Maxime Hadjinlian
2015-10-03 18:21 ` Arnout Vandecappelle
2015-10-03 16:45 ` [Buildroot] [PATCH 3/4] libnfs: Without native RPC use libtirpc Maxime Hadjinlian
2015-10-03 18:22 ` Arnout Vandecappelle [this message]
2015-10-03 16:45 ` [Buildroot] [PATCH 4/4] kodi: " Maxime Hadjinlian
2015-10-03 18:25 ` Arnout Vandecappelle
2015-10-03 18:13 ` [Buildroot] [PATCH 1/4] toolchain-external: Remove BLACKFIN_UCLINUX_2012R2 Arnout Vandecappelle
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=56101CF0.2070006@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.