What is the purpose of the libtirpc patch? It builds fine without it on
development LFS. I notice that the rpc-headers tarball does not contain
all of the rpcsvc/ headers, is this the reason for the patch? From a
casual glance, it doesn't appear so. I don't see anything in the three
omitted files that would keep them from building (except possibly the
exclusion of <rpc/netdb.h> which I suspect is not included in <netdb.h>
on unpatched glibc). Ultimately, libnsl and librpc will contain all of
the necessary symbols until a new major version of glibc. So, my
question is, should we be installing the headers separately at all, or
should libtirpc be using a local copy of the needed headers until it
provides its own complete implementation?
Ultimately, we are providing old functionality via glibc, that is not
intended to carry on beyond the next major version. Wouldn't it be
better to provide these headers only to libtirpc, and then symlink the
installed headers into /usr, or better, patch dependent packages to use
the /usr/include/tirpc/rpc{,svc}/ path? I think I might put a bit more
time into this, but I'd like to hear specific details regarding the
above points from those who have worked on it thus far. Since I don't
have a real 7.0 build laying around, I'm gonna rebuild glibc quick
without the patch and see what is actually in the installed headers.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
