Changeset 460ac758 for chapter06/adjustingtoolchain.xml

Timestamp:

08/19/2003 05:07:26 PM (21 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

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

Children:

85d2668

Parents:

503e1a6

Message:

move adjusting toolchain back to where it belonged

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

File:

• chapter06/adjustingtoolchain.xml (modified) (2 diffs)

chapter06/adjustingtoolchain.xml

@@ -3 +3 @@
 <?dbhtml filename="adjustingtoolchain.html" dir="chapter06"?>
 
+<para>Now that we have compiled all the necessary tools, it is time to
+re-adjust our toolchain. We will set it up so that it will link any newly
+compiled program against the new Glibc. Basically, this is the reverse of
+what we did in the "Locking in" stage in the beginning of chapter 5.</para>
+
+<para>The first thing to do is to adjust the linker scripts. For this we
+retained the <filename class="directory">binutils-build</filename>
+directory from the second pass over Binutils. Run the following:</para>
+
 <para><screen><userinput>cd binutils-build
-make -C ld INSTALL=/stage1/bin/install install-data-local
+make -C ld INSTALL=/stage1/bin/install install-data-local</userinput></screen></para>
 
-SPECFILE=/stage1/lib/gcc-lib/*/*/specs
+<para>This installs the adjusted linker scripts. The linker scripts contain
+no mention of <filename class="directory">/stage1/lib</filename> anymore.
+From now on every compiled program will link <emphasis>only</emphasis>
+against the libraries in <filename>/usr/lib</filename> and
+<filename>/lib</filename>. The extra
+<userinput>INSTALL=/stage1/bin/install</userinput> is needed because the
+Makefile created during the second pass still contains the reference to
+<filename>/usr/bin/install</filename>, which we obviously haven't installed
+yet.</para>
+
+<para>You can now remove the Binutils source and build directories.</para>
+
+<para>The next thing to do is to amend our GCC specs file so that it points
+to the new dynamic linker. Just like earlier on, we use a sed to accomplish
+this:</para>
+
+<para><screen><userinput>SPECFILE=/stage1/lib/gcc-lib/*/*/specs
 sed -e 's@/stage1/lib/ld.so.1@/lib/ld.so.1@g' \
 &nbsp;&nbsp;&nbsp;&nbsp;-e 's@/stage1/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' $SPECFILE > XX
@@ -12 +37 @@
 unset SPECFILE</userinput></screen></para>
 
+<para>Again, cutting and pasting the above is recommended. And just like
+before, it is a good idea to check the linker scripts and the specs file o
+ensure the intended changes were actually made.</para>
+
+<para>Note that the linker scripts will still contain a reference to
+<filename class="directory">/stage1/i686-pc-linux-gnu/lib</filename>. This
+is unavoidable, but luckily does not present a problem. There are no
+libraries in that location as all the temporary stage1 libraries are
+located in <filename class="directory">/stage1/lib</filename>.</para>
+
 </sect1>