DJ Lucas wrote: > What a disaster! Even RedHat hasn't got this far yet. There is more we > need to do to GLibc than install the headers. I'm suggesting that we > follow suit, as the rest of the distros have, and re-export the symbols > in LFS and continue to install the headers until a *complete* > replacement is available.
Have you looked at glibc in the current LFS svn? > Also, OpenSSL will likely be a requirement soon for TI-RPC's crypto > libs. As far as BLFS is concerned, we can make the assumption that the > eratta was followed with the above changes made (glibc re-installed for > people who have already built LFS-7.0), or just stick with what is there > now and delete the static libs for TI-RPC, but that does mean that NIS > is completely dead (and the shared TI-RPC is still potentially broken). BLFS installs the headers if they are working from LFS7. Yes, NIS is broken. I don't want to tackle that until it is fixed upstream. Does anyone still use NIS? A BLFS builder probably should use LDAP instead. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
