From: Lars Wendler <polynomial-c@gmx.de>
To: linux-nfs@vger.kernel.org
Subject: 2.9.2 release: --disable-nfsdctl breaks build
Date: Sat, 1 Aug 2026 17:53:46 +0200 [thread overview]
Message-ID: <20260801175346.4d948b87@chagall.paradoxon.rec> (raw)
Hi,
trying to test 2.9.2 release I stumbled upon a compile error using
this set of configure switches:
--disable-static --with-statedir=/var/lib/nfs --enable-tirpc
--with-tirpcinclude=/usr/include/tirpc/
--with-pluginpath=/usr/lib64/libnfsidmap --with-rpcgen
--with-systemd=/usr/lib/systemd/system --without-gssglue --enable-caps
--enable-ipv6 --disable-junction --disable-gss --disable-svcgss
--disable-ldap --enable-libmount-mount --disable-nfsdctl --enable-nfsv4
--enable-blkmapd --enable-nfsdcld --enable-nfsdcltrack
--enable-nfsv4server --enable-uuid --without-krb5 --without-tcp-wrappers
Here's the error:
libtool: link: x86_64-pc-linux-gnu-gcc -Wall -Wextra
-Werror=strict-prototypes - fno-strict-aliasing -march=native
-mtune=native -O2 -pipe -Wl,-O1 -Wl,--hash-style=gnu -Wl,--sort-common
-Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,pack-relative-relocs -o
exportfs exportfs-exportfs.o -Wl,--as-needed
../../support/export/libexport.a ../../support/nfs/.libs/libnfs.a
-luuid ../../support/misc/libmisc.a
../../support/reexport/libreexport.a -lpthread -lnl-genl-3 -lnl-3
-lresolv
/usr/x86_64-pc-linux-gnu/binutils-bin/2.47/ld: exportfs-exportfs.o: in
function `unexportfs_parsed':
exportfs.c:(.text+0xfbe): undefined reference to `nfsd_nl_cmd_str'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:535: exportfs] Error 1
make[2]: Leaving directory
'/var/tmp/portage/net-fs/nfs-utils-2.9.2/work/nfs-utils-2.9.2/utils/exportfs'
Switching --disable-nfsdctl to --enable-nfsdctl in the above set of
configure flags makes the build succeed.
Kind regards
Lars
reply other threads:[~2026-08-01 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260801175346.4d948b87@chagall.paradoxon.rec \
--to=polynomial-c@gmx.de \
--cc=linux-nfs@vger.kernel.org \
/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