summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorRoland McGrath <roland@gnu.org>2005-04-15 09:33:04 +0000
committerRoland McGrath <roland@gnu.org>2005-04-15 09:33:04 +0000
commit6183d906dd822337dec18dd1f48209dfd17127bd (patch)
tree23fe554ffcdecf0ae3b5879155c28b17766ea441 /FAQ
parenta19fc30a4be27a24065b9a53b98042b73ff51b69 (diff)
downloadglibc-6183d906dd822337dec18dd1f48209dfd17127bd.tar.gz
Updated to fedora-glibc-20050415T0909cvs/fedora-glibc-2_3_5-1
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ16
1 files changed, 16 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index 6d95ef332d..77bd47e3ed 100644
--- a/FAQ
+++ b/FAQ
@@ -48,6 +48,8 @@ please let me know.
malloc/libmemprof.so. How can I fix this?
1.20. Which tools should I use for MIPS?
1.21. Which compiler should I use for powerpc64?
+1.22. `make' fails when running rpcgen the first time,
+ what is going on? How do I fix this?
2. Installation and configuration issues
@@ -573,6 +575,20 @@ 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).
+
+1.22. `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.
+
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .