All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] autofs: allow to use libtirpc instead of internal C implementation
Date: Sun, 2 Apr 2017 05:40:08 +0200	[thread overview]
Message-ID: <20170402034008.GB5361@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170323071058.GA29887@waldemar-brodkorb.de>

ping?

Waldemar Brodkorb wrote,

> uClibc-ng plans to remove internal RPC implementation as it
> is ipv4 only and can not be used for most important RPC software
> rpcbind and nfs-utils.
> musl does not implement RPC and GNU C library deprecated the
> internal implementation a while ago.
> It is still possible to use the C library implementation.
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---                                                                                                                                                                       
> v1 -> v2:                                                                                                                                                                 
>   - Thomas Petazzoni wants to keep legacy C library provided RPC support  
> v2 -> v3:
>   - combine with BR2_PACKAGE_LIBTIRPC conditionally, suggested by Baruch Siach

  reply	other threads:[~2017-04-02  3:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  7:10 [Buildroot] [PATCH v3] autofs: allow to use libtirpc instead of internal C implementation Waldemar Brodkorb
2017-04-02  3:40 ` Waldemar Brodkorb [this message]
2017-04-08 14:05 ` Thomas Petazzoni
2017-04-08 19:03   ` Waldemar Brodkorb
2017-04-08 19:38     ` Thomas Petazzoni
2017-04-10  5:33       ` Waldemar Brodkorb

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=20170402034008.GB5361@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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.