aboutsummaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-10-20 21:18:11 +0000
committerUlrich Drepper <drepper@redhat.com>1998-10-20 21:18:11 +0000
commit48244d09317581396dc0c22bdb69489dc0ea4c5a (patch)
tree264b5c6adf13451da3abce523a64e459d3535ace /FAQ.in
parent10411f2d14f7a567c0a38811e111751d33a4b3e8 (diff)
downloadglibc-48244d09317581396dc0c22bdb69489dc0ea4c5a.tar
glibc-48244d09317581396dc0c22bdb69489dc0ea4c5a.tar.gz
glibc-48244d09317581396dc0c22bdb69489dc0ea4c5a.tar.bz2
glibc-48244d09317581396dc0c22bdb69489dc0ea4c5a.zip
Update.
* math/tgmath.h: Make nested function calls work.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in12
1 files changed, 12 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index 197d5a6fba..bdab8de6e5 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -731,6 +731,18 @@ an installation of glibc that is configured with --prefix=/usr should help
detect these situations. If the script reports problems, something is
really screwed up.
+?? When I use nscd the machine freezes.
+
+{UD} It is well known that you cannot use nscd with Linux 2.0.*. There
+is functionality missing in the kernel and work-arounds are not suitable.
+Beside this some parts of the kernel are too buggy when it comes to using
+threads.
+
+So you have the possibilities to run Linux 2.0.* or update to a higher
+version and start using nscd.
+
+Note that I have at this point no information about any other platform.
+
? Source and binary incompatibilities, and what to do about them
?? I expect GNU libc to be 100% source code compatible with