source: chapter06/adjustingtoolchain.xml@ 1e163254

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 1e163254 was e69ecfb1, checked in by Gerard Beekmans <gerard@…>, 21 years ago

Removed mention of INSTALL=... from the text. It was removed from the command yesterday

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

  • Property mode set to 100644
File size: 2.2 KB
Line 
1<sect1 id="ch06-adjustingtoolchain">
2<title>Re-adjusting the toolchain</title>
3<?dbhtml filename="adjustingtoolchain.html" dir="chapter06"?>
4
5<para>Now that the new C libraries have been installed, it's time to re-adjust
6our toolchain. We'll adjust it so that it will link any newly compiled program
7against the new C libraries. Basically, this is the reverse of what we did
8in the "Locking in" stage in the beginning of the previous chapter.</para>
9
10<para>The first thing to do is to adjust the linker scripts. For this we
11retained the source and build directories from the second pass over Binutils.
12Install the adjusted linker scripts by running the following from within the
13<filename class="directory">binutils-build</filename> directory:</para>
14
15<para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
16
17<para>The linker scripts now contain
18no mention of <filename class="directory">/tools/lib</filename> anymore.
19From now on every compiled program will link <emphasis>only</emphasis>
20against the libraries in <filename>/usr/lib</filename> and
21<filename>/lib</filename>.</para>
22
23<para>You can now remove the Binutils source and build 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. Just like earlier on, we use a sed to accomplish
27this:</para>
28
29<para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs
30sed -e 's@/tools/lib/ld.so.1@/lib/ld.so.1@g' \
31&nbsp;&nbsp;&nbsp;&nbsp;-e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \
32&nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE > newspecfile
33mv newspecfile $SPECFILE
34unset SPECFILE</userinput></screen></para>
35
36<para>Again, cutting and pasting the above is recommended. And just like
37before, it is a good idea to check the linker scripts and the specs file to
38ensure the intended changes were actually made.</para>
39
40<para>Note that the linker scripts will still contain a reference to
41<filename class="directory">/tools/i686-pc-linux-gnu/lib</filename>. This
42is unavoidable, but luckily does not present a problem. There are no
43libraries in that location as all the temporary tools libraries are
44located in <filename class="directory">/tools/lib</filename>.</para>
45
46</sect1>
47
Note: See TracBrowser for help on using the repository browser.