From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/nfs-utils: enable IPv6
Date: Mon, 9 Sep 2019 10:03:05 +0200 [thread overview]
Message-ID: <20190909100305.6ed6662d@windsurf> (raw)
In-Reply-To: <20190812173712.23202-1-unixmania@gmail.com>
Hello,
Arnout, Peter added in Cc, see below.
On Mon, 12 Aug 2019 14:37:12 -0300
unixmania at gmail.com wrote:
> From: Carlos Santos <unixmania@gmail.com>
>
> IPv6 requires libtirpc, so select BR2_PACKAGE_LIBTIRPC inconditionally.
>
> Fixes: https://bugs.busybox.net/show_bug.cgi?id=10806
>
> Signed-off-by: Carlos Santos <unixmania@gmail.com>
Arnout, Peter, do you have an opinion about this change ?
Basically, this change makes libtirpc mandatory for nfs-utils, because
it is necessary to have IPv6 RPC support.
However, libtirpc is always necessary if you want RPC on IPv6, so if we
take the decision of making libtirpc mandatory for nfs-utils, we should
make it mandatory for all packages that use RPC support, and remove the
support for RPC from the toolchain.
My opinion is that we should keep things are they are today: nfs-utils
uses libtirpc if it's there, and otherwise uses the toolchain RPC
support. If a user wants IPv6 support, he should enable libtirpc.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-09 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 17:37 [Buildroot] [PATCH v2] package/nfs-utils: enable IPv6 unixmania at gmail.com
2019-09-09 8:03 ` Thomas Petazzoni [this message]
2019-09-09 9:16 ` Arnout Vandecappelle
2019-09-09 23:56 ` [Buildroot] [PATCH v2] package/nfs-utils: enable IPv6 if libtirpc is selected unixmania at gmail.com
2019-09-10 7:06 ` Arnout Vandecappelle
2019-09-10 10:29 ` Carlos Santos
2019-09-10 10:55 ` Thomas Petazzoni
2019-09-10 11:03 ` Carlos Santos
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=20190909100305.6ed6662d@windsurf \
--to=thomas.petazzoni@bootlin.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