summaryrefslogtreecommitdiff
path: root/hurd/debugging/glibc.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-10-19 11:57:21 +0200
committerThomas Schwinge <thomas@schwinge.name>2010-10-19 11:59:57 +0200
commit3c6af50a5777f78b16b71fbeb28445d4af40ef4a (patch)
tree19950613cd528cc825b5d923a80c55f5b6fd0154 /hurd/debugging/glibc.mdwn
parentc66c60403a40b9dd0ea105e63b9a34a4ee56ba84 (diff)
Reorganize some toolchain pages.
Diffstat (limited to 'hurd/debugging/glibc.mdwn')
-rw-r--r--hurd/debugging/glibc.mdwn11
1 files changed, 5 insertions, 6 deletions
diff --git a/hurd/debugging/glibc.mdwn b/hurd/debugging/glibc.mdwn
index 905dd0da..e9817132 100644
--- a/hurd/debugging/glibc.mdwn
+++ b/hurd/debugging/glibc.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2007, 2008, 2010 Free Software Foundation,
+Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -15,7 +16,7 @@ glibc have been done.
First step is having the build of glibc succeed. This is actually more
difficult than one might expect as it involves (towards the end of the build
-process -- unless you are [[building/cross-compiling]], of course -- that the
+process -- unless you are cross-compiling, of course -- that the
newly created libraries and loader actually work: they'll be used to run the
`rpcgen` program. If that step doesn't succeed, it'll look similar to this:
@@ -25,12 +26,10 @@ newly created libraries and loader actually work: they'll be used to run the
---
-Unless [[building/cross-compiling]], the next thing you'll probably want to do
+Unless cross-compiling, the next thing you'll probably want to do
is running the test suite, or parts of it.
-Here is a list of known failures:
-
-[TODO].
+There is a list of [[known failures|open_issues/glibc_testsuite]].
---