summary refs log tree commit diff
path: root/FAQ
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-09-05 23:34:47 +0000
committerUlrich Drepper <drepper@redhat.com>1999-09-05 23:34:47 +0000
commitbd952512eac147864ad25e8bcca5c5094b0d958a (patch)
tree7fdfd8e40cefa6c0797ab5893950c315a4ac7e4b /FAQ
parent5bb17dca42994797eff18bfe9707072dd9543bc7 (diff)
downloadglibc-bd952512eac147864ad25e8bcca5c5094b0d958a.tar.gz
glibc-bd952512eac147864ad25e8bcca5c5094b0d958a.tar.xz
glibc-bd952512eac147864ad25e8bcca5c5094b0d958a.zip
Update.
1999-08-31  H.J. Lu  <hjl@gnu.org>

	* nscd/nscd_getgr_r.c (nscd_getgr_r): Cleanup the buffer count.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ8
1 files changed, 8 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index 5090e634f9..0ab96c7aad 100644
--- a/FAQ
+++ b/FAQ
@@ -237,6 +237,9 @@ Make up your own decision.
 GNU CC versions 2.95 and above are derived from egcs, and they may do even
 better.
 
+Please note that gcc 2.95 and 2.95.1 cannot compile glibc on Alpha due to
+problems in the complex float support.
+
 
 1.3.	When I try to compile glibc I get only error messages.
 	What's wrong?
@@ -403,6 +406,11 @@ files, provide support for additional architectures, and just about anything
 else.  The existing makefiles do most of the work; only some few stub rules
 must be written to get everything running.
 
+Most add-ons are tightly coupled to a specific GNU libc version.  Please
+check that the add-ons work with the GNU libc.  For example the crypt and
+linuxthreads add-ons have the same numbering scheme as the libc and will in
+general only work with the corresponding libc.
+
 
 1.12.	My XXX kernel emulates a floating-point coprocessor for me.
 	Should I enable --with-fp?