mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-02-07 23:03:17 +00:00
313ca76210
Also moved a note about saving the /tools directory to the beginning of chapter 6. Fixes bug 1677. Thanks to Chris Staub, Alexander Patrakov, Greg Schafer and Tushar Teredesai for reporting and resolving this issue. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7306 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
89 lines
3.8 KiB
XML
89 lines
3.8 KiB
XML
<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|
<!ENTITY % general-entities SYSTEM "../general.ent">
|
|
%general-entities;
|
|
]>
|
|
<sect1 id="ch-system-readjusting">
|
|
<title>Re-adjusting the Toolchain</title>
|
|
<?dbhtml filename="readjusting.html"?>
|
|
|
|
<para>Now that the final C libraries have been installed, it is time to adjust
|
|
the toolchain again. The toolchain will be adjusted so that it will link any
|
|
newly compiled program against these new libraries. This is a similar process
|
|
used in the <quote>Adjusting</quote> phase in the beginning of <xref
|
|
linkend="chapter-temporary-tools"/>, but with the adjustments reversed. In <xref
|
|
linkend="chapter-temporary-tools"/>, the chain was guided from the host's
|
|
<filename class="directory">/{,usr/}lib</filename> directories to the new
|
|
<filename class="directory">/tools/lib</filename> directory. Now, the chain will
|
|
be guided from that same <filename class="directory">/tools/lib</filename>
|
|
directory to the LFS <filename class="directory">/{,usr/}lib</filename>
|
|
directories.</para>
|
|
|
|
<para>First, amend the GCC specs file so that it points to the new
|
|
dynamic linker. A <command>sed</command> command accomplishes this:</para>
|
|
|
|
<screen><userinput>SPECFILE=`dirname $(gcc -print-libgcc-file-name)`/specs &&
|
|
gcc -dumpspecs > $SPECFILE &&
|
|
sed -i 's@^/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' $SPECFILE &&
|
|
unset SPECFILE</userinput></screen>
|
|
|
|
<para>It is a good idea to visually inspect the specs file to verify the intended
|
|
change was actually made.</para>
|
|
|
|
<important><para>If working on a platform where the name of the
|
|
dynamic linker is something other than
|
|
<filename class="libraryfile">ld-linux.so.2</filename>, substitute
|
|
<quote>ld-linux.so.2</quote> with the name of the platform's
|
|
dynamic linker in the above commands. Refer back to <xref
|
|
linkend="ch-tools-toolchaintechnotes" role=","/> if
|
|
necessary.</para></important>
|
|
|
|
<para>Now create temporary wrapper scripts for <filename>gcc</filename> and
|
|
<filename>ld</filename>. These scripts will point to their real counterparts
|
|
in <filename class="directory">/tools</filename> but with adjusted parameters
|
|
to ensure that GCC in the next section links to our newly installed Glibc.</para>
|
|
|
|
<screen><userinput>cat > /usr/bin/gcc << "EOF"
|
|
#!/bin/bash
|
|
/tools/bin/gcc -B/usr/lib $@
|
|
EOF
|
|
cat > /usr/bin/ld << "EOF"
|
|
#!/bin/bash
|
|
/tools/bin/ld -nostdlib -L/usr/lib -L/lib $@
|
|
EOF
|
|
chmod 755 /usr/bin/{ld,gcc}
|
|
ln -s gcc /usr/bin/cc</userinput></screen>
|
|
|
|
<caution><para>It is imperative at this point to stop and ensure that
|
|
the basic functions (compiling and linking) of the adjusted toolchain
|
|
are working as expected. To do this, perform a sanity
|
|
check:</para>
|
|
|
|
<screen><userinput>echo 'main(){}' > dummy.c
|
|
cc dummy.c
|
|
readelf -l a.out | grep ': /lib'</userinput></screen>
|
|
|
|
<para>If everything is working correctly, there should be no errors,
|
|
and the output of the last command will be (allowing for
|
|
platform-specific differences in dynamic linker name):</para>
|
|
|
|
<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
|
|
|
|
<para>Note that <filename class="directory">/lib</filename> is now
|
|
the prefix of our dynamic linker.</para>
|
|
|
|
<para>If the output does not appear as shown above or is not received
|
|
at all, then something is seriously wrong. Investigate and retrace the
|
|
steps to find out where the problem is and correct it. The most likely
|
|
reason is that something went wrong with the specs file amendment
|
|
above. Any issues will need to be resolved before continuing on with
|
|
the process.</para>
|
|
|
|
<para>Once everything is working correctly, clean up the test
|
|
files:</para>
|
|
|
|
<screen><userinput>rm -v dummy.c a.out</userinput></screen></caution>
|
|
|
|
</sect1>
|
|
|