Thanks Ken -
Yes, I was using the latest LFS & BLFS books checked out from SVN - not GIT -
that was a typo, sorry - and yes the versions I read are both version 8.0 -
the latest versions checked out from SVN a few days ago.
But neither LFS nor BLFS make any mention of this glibc NIS / RPC
header issue -
@ LFS-BOOK.html#ch-tools-glibc , it says:
./configure \
--prefix=/tools \
--host=$LFS_TGT \
--build=$(../scripts/config.guess) \
--enable-kernel=2.6.32 \
--with-headers=/tools/include \
libc_cv_forced_unwind=yes \
libc_cv_c_cleanup=yes
There is no mention of :
--enable-obsolete-rpc --enable-obsolete-nsl
which are necessary to generate the NIS & RPC headers,
nor that I needed to do a separate :
$ make subdirs='sunrpc nis' install_root=$DESTDIR install
in order to get the headers installed .
But they are now, finally!
But libtirpc still doesn't build - I will update when figure out why not.
Thanks & Regards,
Jason
On 28/05/2017, Ken Moffat <[email protected]> wrote:
> On Sun, May 28, 2017 at 01:41:29PM +0000, Jason Vas Dias wrote:
>> Hi Linux from Scratch-ers -
>>
>> I've been building my own linux distro since @ 1998 and
>> running a largely LFS based / compliant system on my current x86_64
>> (i7-4910MQ) Clevo Laptop for the past couple of years .
>> Great System!
>>
>> Recently came across my first major stumbling block , now having
>> a need for RPC + NFS + Kerberos, I find I am unable to build
>> libtirpc-1.0.1 according to the instructions in the latest GIT
>> draft of BLFS (2016-10-15 20:13:31 +0000 (Sat, 15 Oct 2016))
> ^^^^^^^^^^^^^^^^^^^^
> (keeping the rest, for context)
>> or in libtirpc documentation -
>>
>> o GLIBC (2.24+ - I am running 2.25) does not ship the rpcsvc/nis.h
>> headers anymore - libtirpc builds fail with:
>>
>> ${SRC}/libtirpc-1.0.1/src/rpc_soc.c:64:24: fatal error: rpcsvc/nis.h: \
>> No such file or directory
>>
>> Similarly, any attempt to build rpcbind of course also fails.
>>
>> There are loads of glibc headers to do with NIS and RPC in
>> /usr/include/{nis,rpc,rpcsvc}/*
>> that glibc used to ship, but now does not.
>>
>> 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.
>>
>> My first attempts to build glibc 'make subdirs=nis install' did not
>> install the headers,
>> and of course attempts to copy the internal headers into /usr/include
>> result in a
>> terrible mess.
>>
>> I have recompiled glibc with those configure options and still I do
>> not get an rpcsvc/nis.h .
>>
>> Anyone seen / overcome this problem yet ?
>>
>> Any pointers on developing glibc patches to ship the old NIS & RPC
>> headers correctly ?
>>
>> I believe the BLFS sections on NIS & RPC & glibc & libtirpc & rpcbind
>> could
>> use some updating on this issue .
>>
>> Any help or advice gratefully received .
>>
>> I am considering just building the Linux BSD newlib port / installing
>> FreeBSD ...
>>
> For the moment, if you find a git version of BLFS (or LFS) it is
> somebody's unofficial fork. We're still using subversion.
>
> We moved LFS to glibc-2.25 before the 8.0 release, so I suggest you
> look either at the BLFS 8.0 stable book or BLFS svn (current version
> is 2017-05-27) for general BLFS packages.
>
> http://www.linuxfromscratch.org/blfs/read.html
> http://www.linuxfromscratch.org/blfs/view/svn/
>
> However, we are still building glibc with --enable-obsolete-rpc :
>
> http://www.linuxfromscratch.org/lfs/view/development/chapter06/glibc.html
>
> and yes, nfs (v2, v3) is working like this. But your mention of
> kerberos suggests you want to use nfs v4 or later - we don't have any
> instructions for that. You will need to not disable gssapi when
> building libtirpc, and therefore you will need an existing kerberos.
> Beyond that I have no idea, kerberos scares me.
>
> 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.
>
> ĸ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
>
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
