From: Ulrich Drepper Date: Tue, 23 Nov 1999 17:19:38 +0000 (+0000) Subject: Regenerated: /usr/unsupported/bin/perl scripts/gen-FAQ.pl FAQ.in X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=72909ba009917002e5bb4e2892296e1ea333d14d;p=thirdparty%2Fglibc.git Regenerated: /usr/unsupported/bin/perl scripts/gen-FAQ.pl FAQ.in --- diff --git a/FAQ b/FAQ index 0409a58a69c..c84ea22effe 100644 --- a/FAQ +++ b/FAQ @@ -1100,11 +1100,11 @@ shadow_compat: nis that have been linked against glibc 2.0 will continue to work. If you compile your own binaries against glibc 2.1, you also need to -recompile some other libraries. The problem is that libio had to be -changed and therefore libraries that are based or depend on the libio -of glibc, e.g. ncurses or slang, need to be recompiled. If you -experience strange segmentation faults in your programs linked against -glibc 2.1, you might need to recompile your libraries. +recompile some other libraries. The problem is that libio had to be changed +and therefore libraries that are based or depend on the libio of glibc, +e.g. ncurses, slang and most C++ libraries, need to be recompiled. If you +experience strange segmentation faults in your programs linked against glibc +2.1, you might need to recompile your libraries. Another problem is that older binaries that were linked statically against glibc 2.0 will reference the older nss modules (libnss_files.so.1 instead of