From: Ulrich Drepper Date: Tue, 23 Nov 1999 17:47:03 +0000 (+0000) Subject: Update. X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0b6cbafe7fcc9148ad76575815098922f68e09c7;p=thirdparty%2Fglibc.git Update. --- diff --git a/ChangeLog b/ChangeLog index c38462058d9..d267f286aa9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +1999-11-23 Thorsten Kukuk + + * iconv/skeleton.c: Don't access next_step->fct if data->is_last + is true. + 1999-11-22 Andreas Jaeger * sunrpc/rpc_clntout.c (printbody): Fix -CLMNab output. diff --git a/FAQ.in b/FAQ.in index 8cd938dabeb..f84ac2a2bba 100644 --- a/FAQ.in +++ b/FAQ.in @@ -898,11 +898,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 diff --git a/linuxthreads_db/ChangeLog b/linuxthreads_db/ChangeLog index ecd407a30b0..bb5b019f392 100644 --- a/linuxthreads_db/ChangeLog +++ b/linuxthreads_db/ChangeLog @@ -1,3 +1,7 @@ +1999-11-23 Ulrich Drepper + + * Makefile: Correct dependency for shared object. + 1999-11-22 Ulrich Drepper * td_ta_map_lwp2thr.c: Add missing brace in comparison.