From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autofs: use libtirpc instead of internal C implementation
Date: Wed, 22 Mar 2017 03:09:46 +0100 [thread overview]
Message-ID: <20170322020946.GF28589@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170321222449.5ceb21f4@free-electrons.com>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> 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?
> What about instead:
>
> select BR2_PACKAGE_LIBTIRPC if !BR2_TOOLCHAIN_HAS_NATIVE_RPC
>
> and adjust the .mk file accordingly.
The idea was to entirely remove BR2_TOOLCHAIN_HAS_NATIVE_RPC in
further patches. This would involve to disable deprecated RPC in
internal Glibc and uClibc-ng toolchains.
I think RPC support in external toolchains will disappear when
GNU C library will finally remove the code.
best regards
Waldemar
next prev parent reply other threads:[~2017-03-22 2:09 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 [this message]
2017-03-22 7:59 ` Thomas Petazzoni
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=20170322020946.GF28589@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox