diff options
author | Ulrich Drepper <drepper@redhat.com> | 1999-11-23 17:47:25 +0000 |
---|---|---|
committer | Ulrich Drepper <drepper@redhat.com> | 1999-11-23 17:47:25 +0000 |
commit | 70cafe50407015324db5ad3105955dbbb2172107 (patch) | |
tree | 901eed19032f409a3c8d511cbbcfd46f345afee9 /FAQ.in | |
parent | aaa8d85c286eace542b14f1030ace7f3cb20ab95 (diff) | |
download | glibc-70cafe50407015324db5ad3105955dbbb2172107.zip glibc-70cafe50407015324db5ad3105955dbbb2172107.tar.gz glibc-70cafe50407015324db5ad3105955dbbb2172107.tar.bz2 |
Update.
* iconv/skeleton.c: Don't access next_step->fct if data->is_last
Diffstat (limited to 'FAQ.in')
-rw-r--r-- | FAQ.in | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -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 |