aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/lockingglibc.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter05/lockingglibc.xml')
-rw-r--r--chapter05/lockingglibc.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/chapter05/lockingglibc.xml b/chapter05/lockingglibc.xml
index 694e529b3..a8360ca51 100644
--- a/chapter05/lockingglibc.xml
+++ b/chapter05/lockingglibc.xml
@@ -17,23 +17,23 @@ directory:</para>
pass of Binutils, and contain no mention of <filename>/lib</filename>,
<filename>/usr/lib</filename> or <filename>/usr/local/lib</filename>.
From this point onwards everything will link <emphasis>only</emphasis>
-against the libraries in <filename>/stage1/lib</filename>.</para>
+against the libraries in <filename>/tools/lib</filename>.</para>
<para>You can now remove Binutils' build and source directories.</para>
<para>The other thing to do is to amend our GCC specs file so that it points
to the new dynamic linker. A simple sed will accomplish this:</para>
-<para><screen><userinput>SPECFILE=/stage1/lib/gcc-lib/*/*/specs
-sed -e 's@/lib/ld.so.1@/stage1/lib/ld.so.1@g' \
-&nbsp;&nbsp;&nbsp;&nbsp;-e 's@/lib/ld-linux.so.2@/stage1/lib/ld-linux.so.2@g' \
+<para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs
+sed -e 's@/lib/ld.so.1@/tools/lib/ld.so.1@g' \
+&nbsp;&nbsp;&nbsp;&nbsp;-e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \
&nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE > tempspecfile
mv tempspecfile $SPECFILE
unset SPECFILE</userinput></screen></para>
<para>We recommend that you cut-and-paste the above rather than try and type
it all in. Or you can edit the specs file by hand if you want to: just replace
-"/lib/ld-linux.so.2" with "/stage1/lib/ld-linux.so.2".</para>
+"/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2".</para>
<para>Lastly, there is a possibility that some include files from the host
system have found their way into gcc's private include dir. This can happen
@@ -41,7 +41,7 @@ because of GCC's "fixincludes" process which part of the GCC build. We'll
explain more about this further on in this chapter. For now, run the
following commands to eliminate this possibility.</para>
-<para><screen><userinput>rm -f /stage1/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>
+<para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>
<para>This completes the installation of the self-contained toolchain, which
can now be used to build the rest of the temporary tools.</para>