From f23e9ad457b6bb02d132163b5dd0099343342bd3 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 8 Mar 2007 17:18:06 +0000 Subject: none --- Hurd/DebuggingGlibc.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Hurd/DebuggingGlibc.mdwn b/Hurd/DebuggingGlibc.mdwn index 251e64c0..8ceaedce 100644 --- a/Hurd/DebuggingGlibc.mdwn +++ b/Hurd/DebuggingGlibc.mdwn @@ -2,7 +2,7 @@ Here are some hints about how to approach testing after nontrivial changes to gl ---- -First step is having the build a glibc complete. This involves at one point that the newly created libraries and loader actually work. (Unless you are cross-building, of course). If that step doesn't succeed, it'll look similar to this: +First step is having the build a glibc complete. This is actually more difficult than one might expect, as it involves (towards the end of the build process; unless you are cross-building, of course), that the newly created libraries and loader actually work: they're used to run the _rpcgen_ program. If that step doesn't succeed, it'll look similar to this: [...] CPP='gcc -E -x c-header' [...]/build/elf/ld.so.1 --library-path [...] [...]/build/sunrpc/rpcgen [...] -- cgit v1.2.3