On 01/03/2013 11:41 PM, Bruce Dubbs wrote: > Armin K. wrote: >> As you see, libtirpc is not yet ready to take over RPC stuff. That's why >> Glibc developers introduced --enable-obsolete-rpc switch if an user >> wants to enable RPC API/ABI once again. It is not used in LFS, but few >> of us asked for Glibc's RPC interface to be re-enabled. No one had luck >> with convincing the devs. :P >> >> You can try (again) convincing them lfs-dev mailing list to enable >> Glibc's RPC interface by default (Good luck with that) :-) >> >> This is already second issue with RPC-aware software not in the book. > > Armin, > > We can talk about it here. I haven't looked at the RPC stuff for > several months and then I only used it for testing nfs, but I don't use > it regularly. > > The problem we had with glibc is that upstream removed rpc and we then > added tirpc. I think I recall a problem with portmap so that was > removed from the book. I thought that the only thing > --enable-obsolete-rpc was to install rpc include files. > > I'd like to see a summary of problems and recommended solutions. > > -- Bruce >
--enable-obsolete-glibc switch completely enables RPC interface which means that it installs it's headers and exports it's ABI and API so RPC-aware programs can use glibc's RPC implementation once again. Not enabling that interface can break binary applications that use glibc's RPC interface (not sure if such packages exists, that's just in theory). Also, libtirpc is not yet ready to take over Glibc's implementation. In BLFS, we patch it and remove good piece of code which uses RPC/NIS interface to implement pieces of RPC/NIS interface (RPCception?). It also needs RPC headers from Glibc and we install glibc headers which have definitions of RPC functions exported by Glibc - which are not exported in our case. In that case, you will have to explicitly link software to libtirpc assuming that headers and functions are compatible (libtirpc has it's headers with same names as glibc ones, they are just in /usr/include/tirpc). One example in BLFS book is Samba, we explicitly link it to libtirpc. We also disable NIS in some software which someone could find useful. Some examples are Linux PAM, Qt, KDE-something (workspace maybe?). As for NFS, I think it needs libtirpc, regardless if Glibc RPC interface is available or not. libtirpc provides IPv6 extensions for RPC while Glibc does not. There is not much software that we hacked to use libtirpc just because we follow upstream (which can't be always right) and don't use obsolete RPC implementation. All other distros still re-export RPC interface. By enabling Glibc RPC/NIS implementation we won't hurt anyone, we can just help someone. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
