From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10806] Allow nfs-utils to use ipv6
Date: Sun, 25 Feb 2018 15:57:27 +0000 [thread overview]
Message-ID: <bug-10806-163-CQDrNER8lh@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10806-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10806
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
We decided a few years ago to no longer make ipv6 support in packages optional,
i.e. always assume it is there. Note that even if the kernel is built without
IPv6 support, it is possible to run executables in it that are built with IPv6
support - but obviously no IPv6 connection will ever be made.
So you can just unconditionally enable IPv6 support in nfs-utils. Except,
apparently, nfs-utils requires libtirpc for IPv6 support, as witnessed by this
commit:
commit e23be36ab3a110787917db59618d9f5280457938
Author: Peter Korsgaard <jacmet@sunsite.dk>
Date: Wed Apr 25 22:29:34 2012
nfs-utils: fix build with ipv6 after 2a10c9 (pass --enable-ipv6 to
autotargets configure)
IPv6 support needs the TIRPC library, which we don't have in Buildroot, so
forcibly disable IPv6 support.
Now, that's a commit from 6 years ago, so the situation may have changed.
Therefore, please try if it is possible to build and run nfs-utils *without*
libtirpc and *with* --enable-ipv6. If that works, just enable ipv6
unconditionally. If it doesn't work, add the --enable/disable-ipv6 to the
existing libtirpc condition in nfs-utils.mk. In that case, please also make a
note in the commit message that native RPC is being deprecated so libtirpc (and
therefore IPv6) will be enabled unconditionally in the future.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-02-25 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 16:40 [Buildroot] [Bug 10806] New: Allow nfs-utils to use ipv6 bugzilla at busybox.net
2018-02-25 15:57 ` bugzilla at busybox.net [this message]
2019-08-12 3:08 ` [Buildroot] [Bug 10806] " bugzilla at busybox.net
2019-08-12 3:18 ` bugzilla at busybox.net
2019-08-12 17:39 ` bugzilla at busybox.net
2019-09-10 0:01 ` bugzilla at busybox.net
2019-09-12 17:16 ` bugzilla at busybox.net
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=bug-10806-163-CQDrNER8lh@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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