source: chapter05/lockingglibc.xml@ 238527e

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 238527e was fa2e693, checked in by Greg Schafer <greg@…>, 21 years ago

Small grammar adjustments.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2812 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.4 KB
Line 
1<sect1 id="ch05-locking-glibc">
2<title>"Locking in" Glibc</title>
3<?dbhtml filename="lockingglibc.html" dir="chapter05"?>
4
5<para>Now that the temporary C libraries have been installed, we want all
6the tools compiled in the rest of this chapter to be linked against these
7libraries. To accomplish this, we need to adjust the linker's scripts and the
8compiler's specs file.</para>
9
10<para>First install the adjusted linker scripts by running the following from
11within the <filename class="directory">binutils-build</filename>
12directory:</para>
13
14<para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
15
16<para>These scripts were adjusted a little while back, at the end of the first
17pass of Binutils, and contain no mention of <filename>/lib</filename>,
18<filename>/usr/lib</filename> or <filename>/usr/local/lib</filename>.
19From this point onwards everything will link <emphasis>only</emphasis>
20against the libraries in <filename>/tools/lib</filename>.</para>
21
22<para>Now that the scripts are adjusted, you have to remove the Binutils
23build and source directories.</para>
24
25<para>The next thing to do is to amend our GCC specs file so that it points
26to the new dynamic linker. A simple sed will accomplish this:</para>
27
28<para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs
29sed -e 's@/lib/ld.so.1@/tools/lib/ld.so.1@g' \
30&nbsp;&nbsp;&nbsp;&nbsp;-e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \
31&nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE > tempspecfile
32mv tempspecfile $SPECFILE
33unset SPECFILE</userinput></screen></para>
34
35<para>We recommend that you cut-and-paste the above rather than try and type it
36all in. Or you can edit the specs file by hand if you want to: just replace
37"/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2" and "/lib/ld.so.1" with
38"/tools/lib/ld.so.1".</para>
39
40<para>Lastly, there is a possibility that some include files from the host
41system have found their way into gcc's private include dir. This can happen
42because of GCC's "fixincludes" process which runs as part of the GCC build.
43We'll explain more about this further on in this chapter. For now, run the
44following commands to eliminate this possibility.</para>
45
46<para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>
47
48<para>This completes the installation of the self-contained toolchain, which
49can now be used to build the rest of the temporary tools.</para>
50
51</sect1>
52
Note: See TracBrowser for help on using the repository browser.