On Thu, 2 Nov 2017 20:26:57 +0100 Pierre Labastie <pierre.labas...@neuf.fr> wrote:
> The text tells it removes a check that fails in the partial LFS environment. Pierre, And is that check run during the installation step where his error happened? For the record, glibc-2.26 and later no longer installs a libnss_nis by default: https://bugs.archlinux.org/task/54592 "The NIS(+) name service modules, libnss_nis, libnss_nisplus, and libnss_compat, are deprecated, and will not be built or installed by default. Replacement implementations based on TIRPC, which additionally support IPv6, are available from <https://github.com/thkukuk/libnss_{compat,nis,nisplus}>." and also note for those upgrading an existing glibc: "Since nsswitch.conf is a backup file for filesystem, wouldn't dropping the obsolete-nsl flag require a manual intervention for everyone with a modified nsswitch.conf? As I understand it now, breaking the 'compat' module would force all such users to correct it *before* they update to a new glibc, or they will become immediately unable to fix their system without booting from alternative media or using an emergency shell." It's not clear to me what exactly the new glibc does not like in "modified" nsswitch.conf. Of course, all should be well for a new LFS installation that follows the book. Cheers, Mike Shell -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
