On Sun, May 28, 2017 at 03:54:01PM +0100, Ken Moffat wrote:
 further details re the headers -

> On Sun, May 28, 2017 at 01:41:29PM +0000, Jason Vas Dias wrote:
> >  I have contacted the libc-help mailing list about this , and the best
> >  answer I got was :
> > 
> > On 12/04/2017, Florian Weimer <[email protected]> wrote:
> > > Anyway, libtirpc should really compile without glibc RPC headers because 
> > > the
> > > glibc headers are incompatible (they are restricted to IPv4, after all).  
> > > If you can't
> > > compile libtirpc, you are doing something wrong.
> > >
> > > If you want glibc to install these headers, you need to compile with
> > > --enable-obsolete-rpc and, more recently, --enable-obsolete-nsl.  But 
> > > this should
> > > really be reserved for legacy installations not using libtirpc in a 
> > > system-wide
> > > fashion.

> 
> As to the comments from the glibc list: I'm in the dark about how to
> build libtirpc without the headers.  There was discussion more than
> a year ago (re ipv6) but my understanding was that libtirpc was not
> yet able to build without them.
> 
I've just checked fedora: they use --enable-obsolete-rpc
and --enable-obsolete-nsl (which is for NIS client functions).

Hmm, possibly Thorsten Kukuk wants people to use libnss_compat
https://github.com/thkukuk/libnss_compat/releases (I found that via
his glibc changelog entry on obsolete nsl where he mentions
https://github.com/thkukuk/libnsl is the replacement for NIS
functions.

ĸen
-- 
I live in a city. I know sparrows from starlings.  After that
everything is a duck as far as I'm concerned.  -- Monstrous Regiment
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to