summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2004-12-22 20:10:10 +0000
committerUlrich Drepper <drepper@redhat.com>2004-12-22 20:10:10 +0000
commita334319f6530564d22e775935d9c91663623a1b4 (patch)
treeb5877475619e4c938e98757d518bb1e9cbead751 /FAQ.in
parent0ecb606cb6cf65de1d9fc8a919bceb4be476c602 (diff)
downloadglibc-a334319f6530564d22e775935d9c91663623a1b4.tar.gz
glibc-a334319f6530564d22e775935d9c91663623a1b4.tar.xz
glibc-a334319f6530564d22e775935d9c91663623a1b4.zip
(CFLAGS-tst-align.c): Add -mpreferred-stack-boundary=4.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in13
1 files changed, 0 insertions, 13 deletions
diff --git a/FAQ.in b/FAQ.in
index 227132bc08..4c161cceb6 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -374,19 +374,6 @@ For details check also my page <http://www.suse.de/~aj/glibc-mips.html>.
 {SM} You want to use at least gcc 3.2 (together with the right versions
 of all the other tools, of course).
 
-??	`make' fails when running rpcgen the first time,
-	what is going on? How do I fix this?
-
-{CO} The first invocation of rpcgen is also the first use of the recently
-compiled dynamic loader.  If there is any problem with the dynamic loader
-it will more than likely fail to run rpcgen properly. This could be due to
-any number of problems.
-
-The only real solution is to debug the loader and determine the problem
-yourself. Please remember that for each architecture there may be various
-patches required to get glibc HEAD into a runnable state. The best course
-of action is to determine if you have all the required patches.
-
 ? Installation and configuration issues
 
 ??	Can I replace the libc on my Linux system with GNU libc?