|
@@ -2,38 +2,33 @@
|
|
<title>"Locking in" Glibc</title>
|
|
<title>"Locking in" Glibc</title>
|
|
<?dbhtml filename="lockingglibc.html" dir="chapter05"?>
|
|
<?dbhtml filename="lockingglibc.html" dir="chapter05"?>
|
|
|
|
|
|
-<sect2><title> </title><para> </para></sect2>
|
|
|
|
|
|
+<para>Now that the temporary C libraries have been installed, we want all
|
|
|
|
+the tools compiled in the rest of this chapter to be linked against these
|
|
|
|
+libraries. To accomplish this, we need to adjust the linker's scripts and the
|
|
|
|
+compiler's specs file.</para>
|
|
|
|
|
|
-<sect2>
|
|
|
|
-<title>Installation of the linker scripts</title>
|
|
|
|
-
|
|
|
|
-<para>Run the following command from within the <filename
|
|
|
|
-class="directory">binutils-build</filename> directory:</para>
|
|
|
|
|
|
+<para>First install the adjusted linker scripts by running the following from
|
|
|
|
+within the <filename class="directory">binutils-build</filename>
|
|
|
|
+directory:</para>
|
|
|
|
|
|
<para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
|
|
<para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
|
|
|
|
|
|
-<para>This installs the adjusted linker scripts. Remember they were adjusted
|
|
|
|
-a little while back, at the end of the first pass of Binutils? The linker
|
|
|
|
-scripts now contain no mention of <filename>/lib</filename>,
|
|
|
|
|
|
+<para>These scripts were adjusted a little while back, at the end of the first
|
|
|
|
+pass of Binutils, and contain no mention of <filename>/lib</filename>,
|
|
<filename>/usr/lib</filename> or <filename>/usr/local/lib</filename>.
|
|
<filename>/usr/lib</filename> or <filename>/usr/local/lib</filename>.
|
|
From this point onwards everything will link <emphasis>only</emphasis>
|
|
From this point onwards everything will link <emphasis>only</emphasis>
|
|
against the libraries in <filename>/stage1/lib</filename>.</para>
|
|
against the libraries in <filename>/stage1/lib</filename>.</para>
|
|
|
|
|
|
<para>You can now remove Binutils' build and source directories.</para>
|
|
<para>You can now remove Binutils' build and source directories.</para>
|
|
|
|
|
|
-</sect2>
|
|
|
|
-
|
|
|
|
-<sect2>
|
|
|
|
-<title>Amending GCC's specs file</title>
|
|
|
|
-
|
|
|
|
-<para>The final thing to do is to amend our GCC specs file so that it points
|
|
|
|
|
|
+<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>
|
|
to the new dynamic linker. A simple sed will accomplish this:</para>
|
|
|
|
|
|
<para><screen><userinput>SPECFILE=/stage1/lib/gcc-lib/*/*/specs
|
|
<para><screen><userinput>SPECFILE=/stage1/lib/gcc-lib/*/*/specs
|
|
sed -e 's@/lib/ld.so.1@/stage1/lib/ld.so.1@g' \
|
|
sed -e 's@/lib/ld.so.1@/stage1/lib/ld.so.1@g' \
|
|
-e 's@/lib/ld-linux.so.2@/stage1/lib/ld-linux.so.2@g' \
|
|
-e 's@/lib/ld-linux.so.2@/stage1/lib/ld-linux.so.2@g' \
|
|
- $SPECFILE > XX
|
|
|
|
-mv XX $SPECFILE
|
|
|
|
|
|
+ $SPECFILE > tempspecfile
|
|
|
|
+mv tempspecfile $SPECFILE
|
|
unset SPECFILE</userinput></screen></para>
|
|
unset SPECFILE</userinput></screen></para>
|
|
|
|
|
|
<para>We recommend that you cut-and-paste the above rather than try and type
|
|
<para>We recommend that you cut-and-paste the above rather than try and type
|
|
@@ -43,7 +38,5 @@ it all in. Or you can edit the specs file by hand if you want to: just replace
|
|
<para>This completes the installation of the self-contained toolchain, which
|
|
<para>This completes the installation of the self-contained toolchain, which
|
|
can now be used to build the rest of the temporary tools.</para>
|
|
can now be used to build the rest of the temporary tools.</para>
|
|
|
|
|
|
-</sect2>
|
|
|
|
-
|
|
|
|
</sect1>
|
|
</sect1>
|
|
|
|
|