mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-01-19 21:49:13 +00:00
148bb04f80
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2725 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
51 lines
2.3 KiB
XML
51 lines
2.3 KiB
XML
<sect1 id="ch05-locking-glibc">
|
|
<title>"Locking in" Glibc</title>
|
|
<?dbhtml filename="lockingglibc.html" dir="chapter05"?>
|
|
|
|
<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>
|
|
|
|
<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>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>.
|
|
From this point onwards everything will link <emphasis>only</emphasis>
|
|
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=/tools/lib/gcc-lib/*/*/specs
|
|
sed -e 's@/lib/ld.so.1@/tools/lib/ld.so.1@g' \
|
|
-e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \
|
|
$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 "/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
|
|
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 /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>
|
|
|
|
</sect1>
|
|
|