summaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-11-23 17:47:25 +0000
committerUlrich Drepper <drepper@redhat.com>1999-11-23 17:47:25 +0000
commit70cafe50407015324db5ad3105955dbbb2172107 (patch)
tree901eed19032f409a3c8d511cbbcfd46f345afee9 /FAQ.in
parentaaa8d85c286eace542b14f1030ace7f3cb20ab95 (diff)
downloadglibc-70cafe50407015324db5ad3105955dbbb2172107.tar.gz
Update.
* iconv/skeleton.c: Don't access next_step->fct if data->is_last
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in10
1 files changed, 5 insertions, 5 deletions
diff --git a/FAQ.in b/FAQ.in
index 0907ed8ad1..391e756eac 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -895,11 +895,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