summaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-03-08 18:11:53 +0000
committerUlrich Drepper <drepper@redhat.com>1999-03-08 18:11:53 +0000
commit4f7ea42781ff7b4fe3730c097a929c9f910a7075 (patch)
treee0830c47fd66bb69fc05dfe1a4dee215a191f645 /FAQ.in
parent27e309c17790ac7d0a2163785a2f4633f87b4958 (diff)
Update.
1999-03-08 Ulrich Drepper <drepper@cygnus.com> * locales/ru_RU (mon): Fix March and May month name translations. Reported by Vadim V. Zhytnikov <vvzhy@td.lpi.ac.ru>.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in7
1 files changed, 6 insertions, 1 deletions
diff --git a/FAQ.in b/FAQ.in
index 3a769d8692..ab42dc5924 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -845,7 +845,7 @@ passwd_compat: nis
group_compat: nis
shadow_compat: nis
-?? What needs to be recompiled when upgrading from glibc 2.0 to glibc
+??libs What needs to be recompiled when upgrading from glibc 2.0 to glibc
2.1?
{AJ,CG} If you just upgrade the glibc from 2.0.x (x <= 7) to 2.1, binaries
@@ -907,6 +907,11 @@ compiler uses, compile your program with `gcc -E ...|grep G_config.h' and
remove that file. Your compiler should pick up the file that has been
installed by glibc 2.1 in your include directory.
+?? After upgrading to glibc 2.1, libraries that were compiled against
+ glibc 2.0.x don't work anymore.
+
+{AJ} See ?libs.
+
? Source and binary incompatibilities, and what to do about them