On Thu, 5 Jan 2012 13:57:07 -0500
Jim Rees <rees@xxxxxxxxx> wrote:
> Jeff Layton wrote:
>
> On Sat, 24 Dec 2011 11:53:01 -0500
> Jim Rees <rees@xxxxxxxxx> wrote:
>
> > Jim Rees wrote:
> >
> > Jeff Layton wrote:
> >
> > This patchset is a cleanup of the linking in nfs-utils. This should
> > reduce the number of unnecessary libraries that each of the binaries are
> > linked against.
> >
> > This is probably unrelated to your patches, but here's what I get:
> >
> > ...
> > /bin/bash ../../libtool --tag=CC --mode=link gcc -Wall -Wextra -Wstrict-prototypes -pipe -g -O2 -o nfsidmap nfsidmap.o -lnfsidmap -lkeyutils -lnfsidmap -ltirpc
> > libtool: link: gcc -Wall -Wextra -Wstrict-prototypes -pipe -g -O2 -o nfsidmap nfsidmap.o -lkeyutils -lnfsidmap -ltirpc
> > nfsidmap.o: In function `key_revoke':
> > /home/rees/p/nfs-utils/utils/nfsidmap/nfsidmap.c:153: undefined reference to `xlog_syslog'
> > ...
> >
> > Never mind, cockpit error. I ran autogen in the wrong directory. Now I'm
> > getting this:
> >
> > % configure --prefix=/usr --sysconfdir=/etc --enable-nfsv41 --enable-ipv6 \
> > ? --disable-gss --disable-uuid --enable-tirpc --without-tcp-wrappers \
> > ? --disable-libmount-mount
> > ...
> > checking for bindresvport_sa... no
> > configure: error: Missing library functions needed for IPv6.
>
> Sorry I didn't respond to this sooner...
>
> Did you ever figure out what's going on here? Is this a regression
> caused by this patchset?
>
> No, I didn't. I can try reverting your patch to see what happens if you
> want. Do you know where bindresvport_sa is supposed to come from?
I think libtirpc is supposed to supply that. It's declared in this file
on my machine:
/usr/include/tirpc/rpc/rpc.h
...and libtirpc seems to be exporting it:
$ objdump -T /lib64/libtirpc.so | grep bindresvport
0000000000009220 g DF .text 0000000000000228 Base bindresvport_sa
0000000000009450 g DF .text 0000000000000005 Base bindresvport
--
Jeff Layton <jlayton@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
