From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autofs: use libtirpc instead of internal C implementation
Date: Wed, 22 Mar 2017 08:59:59 +0100 [thread overview]
Message-ID: <20170322085959.587a9f22@free-electrons.com> (raw)
In-Reply-To: <20170322020946.GF28589@waldemar-brodkorb.de>
Hello,
On Wed, 22 Mar 2017 03:09:46 +0100, Waldemar Brodkorb wrote:
> > On Tue, 21 Mar 2017 20:32:13 +0100, Waldemar Brodkorb wrote:
> >
> > > @@ -2,8 +2,8 @@ config BR2_PACKAGE_AUTOFS
> > > bool "autofs"
> > > depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
> > > depends on BR2_USE_MMU
> > > - depends on BR2_TOOLCHAIN_HAS_NATIVE_RPC
> > > depends on !BR2_STATIC_LIBS # dlfcn
> > > + select BR2_PACKAGE_LIBTIRPC
> >
> > Why should we force people to use libtirpc ?
>
> Because the internal RPC implementation is mostly useless and
> getting removed?
I don't quite agree. The one in glibc has been used for years
successfully, and is still useful. So even if uClibc decides to remove
its internal RPC implementation, I'd like to give people the option to
use the internal RPC implementation of glibc.
I agree RPC support in glibc will most likely disappear at some point
in the future, but we're not there yet. So for now, I'd prefer if we
just took the step of dropping RPC support in uClibc, and doing the
necessary changes in packages so that they all build/work fine with
libtirpc. That's anyway a very good preparation step to get rid of
internal RPC support entirely at some point in the future.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-22 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:32 [Buildroot] [PATCH] autofs: use libtirpc instead of internal C implementation Waldemar Brodkorb
2017-03-21 21:24 ` Thomas Petazzoni
2017-03-22 2:09 ` Waldemar Brodkorb
2017-03-22 7:59 ` Thomas Petazzoni [this message]
2017-03-23 21:53 ` Arnout Vandecappelle
2017-03-26 9:22 ` Yann E. MORIN
2017-03-28 17:47 ` 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=20170322085959.587a9f22@free-electrons.com \
--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