aboutsummaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2000-02-23 22:15:49 +0000
committerUlrich Drepper <drepper@redhat.com>2000-02-23 22:15:49 +0000
commitb2b28911645ee10d8a9b843c2d7406abe16a250a (patch)
tree69e1bb2f0d0819962e3cc171b1fc6424d1525823 /FAQ.in
parentc8bcc2eade4f02d43c1511f72eec99bea141866e (diff)
downloadglibc-b2b28911645ee10d8a9b843c2d7406abe16a250a.zip
glibc-b2b28911645ee10d8a9b843c2d7406abe16a250a.tar.gz
glibc-b2b28911645ee10d8a9b843c2d7406abe16a250a.tar.bz2
Update.
2000-02-23 Andreas Jaeger <aj@suse.de> * dlfcn/dlopen.c: Include <stddef.h> for NULL. * dlfcn/dlsym.c: Likewise. * dlfcn/dlvsym.c: Likewise. * iconv/gconv.c: Likewise.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in17
1 files changed, 16 insertions, 1 deletions
diff --git a/FAQ.in b/FAQ.in
index c130a86..0581b35 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -346,7 +346,6 @@ compatibility - forever! The binary compatibility you lose is not only
against the previous version of the GNU libc (version 2.0) but also against
all future versions.
-
?? How can I compile on my fast ix86 machine a working libc for my slow
i386? After installing libc, programs abort with "Illegal
Instruction".
@@ -363,6 +362,22 @@ And you need to tell gcc to only generate i386 code, just add `-mcpu=i386'
{UD} This applies not only to the i386. Compiling on a i686 for any older
model will also fail if the above methods are not used.
+?? `make' complains about a missing dlfcn/libdl.so when building
+ malloc/libmemprof.so. How can I fix this?
+
+{AJ} Older make version (<= 3.78.90) have a bug which was hidden by a bug in
+glibc (<= 2.1.2). You need to upgrade make to a newer or fixed version. A
+patch is available via
+<http://sourceware.cygnus.com//ml/libc-alpha/2000-02/msg00067.html>.
+
+After upgrading make, you should remove the file sysd-sorted in your build
+directory. The problem is that the broken make creates a wrong order for
+one list in that file. The list has to be recreated with the new make -
+which happens if you remove the file.
+
+You might encounter this bug also in other situations where make scans
+directories. I strongly advise to upgrade your make version.
+
? Installation and configuration issues