summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-06-17 17:59:25 +0000
committerUlrich Drepper <drepper@redhat.com>1998-06-17 17:59:25 +0000
commit0e0316f403a4ef8d00bb4c140b9191b0358ba27c (patch)
treeeaade65bb33dc2c067bf4c8211f7f7d16d9e4984 /FAQ.in
parente021cda255e14eebecde2fc1c92446e25a2ee761 (diff)
downloadglibc-0e0316f403a4ef8d00bb4c140b9191b0358ba27c.tar.gz
glibc-0e0316f403a4ef8d00bb4c140b9191b0358ba27c.tar.xz
glibc-0e0316f403a4ef8d00bb4c140b9191b0358ba27c.zip
Update.
1998-06-17  Ulrich Drepper  <drepper@cygnus.com>

	* sysdeps/unix/sysv/linux/alpha/glob.c: Include sys/types.h before
	glob.h.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in5
1 files changed, 5 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index 53889ff4a3..27c22c27ee 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -670,6 +670,11 @@ was a `libc.so' from libc 5 in /lib, which gets searched first.  To fix the
 problem, just delete /lib/libc.so.  You may also need to delete other
 symbolic links in /lib, such as /lib/libm.so if it points to libm.so.5.
 
+{AJ} The perl script test-installation.pl which is run as last step during
+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.
+
 ? Source and binary incompatibilities, and what to do about them
 
 ??	I expect GNU libc to be 100% source code compatible with