On Thu, 2009-06-04 at 06:03 -0400, Steve Dickson wrote: > > Mike Frysinger wrote: > > On Wednesday 03 June 2009 19:59:09 Chuck Lever wrote: > >> On Jun 3, 2009, at 6:44 PM, Mike Frysinger wrote: > >>> On Wednesday 03 June 2009 11:14:44 Steve Dickson wrote: > >>>> Mike Frysinger wrote: > >>>>> the libtirpc package is self described as a "standalone package". i > >>>>> wonder how far that actually goes. wrt NIS, it requires the > >>>>> system C > >>>>> library to provide NIS functionality or you get a build failure in > >>>>> a few > >>>>> files. would be nice if libtirpc were usable without any NIS > >>>>> baggage at > >>>>> all. > >>>> NIS used RPC procedures to communicate. As it stands today > >>>> NIS is currently using the RPC procedures glibc. In the > >>>> future there is a very good chance that NIS will start > >>>> using the RPC procedures in libtirpc especially if > >>>> IPV6 support is needed... > >>>> > >>>> So I'm a bit confused on what you mean by "NIS baggage" > >>>> in the libtirpc package. > >>> you cannot build libtirpc on a system that doesnt provide NIS > >>> functionality. > >>> realistic RPC usage today is NFS related services only (i.e. a NFS > >>> client > >>> mounting a share on a NFS server). > >> Mike, it would help if you could provide the build output so we can > >> see exactly what's failing. > > > > libtirpc does not provide rpcsvc/nis.h > > Hmm... I wonder what it would take to incorporate that file into > libitrpc... rpcgen support. We already have the nis.x file in glibc's copy of the rpcsvc directory. Trond -- 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
