Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libnfs: Without native RPC use libtirpc
Date: Sun, 26 Apr 2015 15:59:51 +0300	[thread overview]
Message-ID: <20150426125951.GL2258@tarshish> (raw)
In-Reply-To: <1430052871-6235-1-git-send-email-maxime.hadjinlian@gmail.com>

Hi Maxime,

On Sun, Apr 26, 2015 at 02:54:30PM +0200, Maxime Hadjinlian wrote:
> As it's done with nfs-utils, use libtirpc when no native rpc support
> exists in the toolchain.
> 
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
>  package/libnfs/Config.in | 5 +----
>  package/libnfs/libnfs.mk | 4 ++++
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/package/libnfs/Config.in b/package/libnfs/Config.in
> index 6642fe4..e9b939f 100644
> --- a/package/libnfs/Config.in
> +++ b/package/libnfs/Config.in
> @@ -1,10 +1,7 @@
>  config BR2_PACKAGE_LIBNFS
>  	bool "libnfs"
> -	depends on BR2_TOOLCHAIN_HAS_NATIVE_RPC
> +	select BR2_PACKAGE_LIBTIRPC if !BR2_TOOLCHAIN_HAS_NATIVE_RPC

What about libtirpc dependencies?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  parent reply	other threads:[~2015-04-26 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 12:54 [Buildroot] [PATCH 1/2] libnfs: Without native RPC use libtirpc Maxime Hadjinlian
2015-04-26 12:54 ` [Buildroot] [PATCH 2/2] kodi: " Maxime Hadjinlian
2015-04-26 12:59 ` Baruch Siach [this message]
2015-04-26 16:13   ` [Buildroot] [PATCH 1/2] libnfs: " Maxime Hadjinlian
2015-04-26 17:08     ` Thomas Petazzoni
2015-08-06  7:16 ` Thomas Petazzoni

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=20150426125951.GL2258@tarshish \
    --to=baruch@tkos.co.il \
    --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