[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[1770019] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
[673b0d8] | 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
| 6 | <sect1 id="ch-system-readjusting">
|
---|
[d72e04a] | 7 | <title>Re-adjusting the Toolchain</title>
|
---|
[673b0d8] | 8 | <?dbhtml filename="readjusting.html"?>
|
---|
| 9 |
|
---|
[81fd230] | 10 | <para>Now that the new and final C libraries have been installed, it
|
---|
| 11 | is time to adjust the toolchain again. The toolchain will be adjusted
|
---|
| 12 | so that it will link any newly compiled program against these new
|
---|
| 13 | libraries. This is the same process used in the
|
---|
| 14 | <quote>Adjusting</quote> phase in the beginning of <xref
|
---|
| 15 | linkend="chapter-temporary-tools"/>, even though it looks to be
|
---|
| 16 | reversed. In <xref linkend="chapter-temporary-tools"/>, the chain was
|
---|
| 17 | guided from the host's <filename
|
---|
| 18 | class="directory">/{,usr/}lib</filename> directories to the new
|
---|
| 19 | <filename class="directory">/tools/lib</filename> directory. Now, the
|
---|
| 20 | chain will be guided from that same <filename
|
---|
| 21 | class="directory">/tools/lib</filename> directory to the LFS
|
---|
| 22 | <filename class="directory">/{,usr/}lib</filename> directories.</para>
|
---|
| 23 |
|
---|
| 24 | <para>Start by adjusting the linker. The source and build directories
|
---|
| 25 | from the second pass over Binutils were retained for this purpose.
|
---|
| 26 | Install the adjusted linker by running the following command from
|
---|
| 27 | within the <filename class="directory">binutils-build</filename>
|
---|
| 28 | directory:</para>
|
---|
[673b0d8] | 29 |
|
---|
| 30 | <screen><userinput>make -C ld INSTALL=/tools/bin/install install</userinput></screen>
|
---|
| 31 |
|
---|
[81fd230] | 32 | <note><para>If the earlier warning to retain the Binutils source and
|
---|
| 33 | build directories from the second pass in <xref
|
---|
| 34 | linkend="chapter-temporary-tools"/> was missed, or if they were
|
---|
| 35 | accidentally deleted or are inaccessible, ignore the above command.
|
---|
| 36 | The result will be that the next package, Binutils, will link against
|
---|
| 37 | the C libraries in <filename class="directory">/tools</filename>
|
---|
| 38 | rather than in <filename class="directory">/{,usr/}lib</filename>.
|
---|
| 39 | This is not ideal, however, testing has shown that the resulting
|
---|
| 40 | Binutils program binaries should be identical.</para></note>
|
---|
| 41 |
|
---|
| 42 | <para>From now on, every compiled program will link only against the
|
---|
| 43 | libraries in <filename class="directory">/usr/lib</filename> and
|
---|
| 44 | <filename class="directory">/lib</filename>. The extra
|
---|
| 45 | <parameter>INSTALL=/tools/bin/install</parameter> option is needed
|
---|
| 46 | because the <filename>Makefile</filename> file created during the
|
---|
| 47 | second pass still contains the reference to
|
---|
| 48 | <command>/usr/bin/install</command>, which has not been installed yet.
|
---|
| 49 | Some host distributions contain a <filename
|
---|
| 50 | class="symlink">ginstall</filename> symbolic link which takes
|
---|
| 51 | precedence in the <filename>Makefile</filename> file and can cause a
|
---|
| 52 | problem. The above command takes care of this issue.</para>
|
---|
| 53 |
|
---|
| 54 | <para>Remove the Binutils source and build directories now.</para>
|
---|
| 55 |
|
---|
| 56 | <para>Next, amend the GCC specs file so that it points to the new
|
---|
[18ea207] | 57 | dynamic linker. A <command>perl</command> command accomplishes this:</para>
|
---|
[673b0d8] | 58 |
|
---|
[6e8fc7d] | 59 | <screen><userinput>perl -pi -e 's@ /tools/lib/ld-linux.so.2@ /lib/ld-linux.so.2@g;' \
|
---|
[2c17ddc] | 60 | -e 's@\*startfile_prefix_spec:\n@$_/usr/lib/ @g;' \
|
---|
[d72e04a] | 61 | `gcc --print-file specs`</userinput></screen>
|
---|
[673b0d8] | 62 |
|
---|
[81fd230] | 63 | <para>It is a good idea to visually inspect the specs file to verify the intended
|
---|
| 64 | change was actually made.</para>
|
---|
| 65 |
|
---|
| 66 | <important><para>If working on a platform where the name of the
|
---|
| 67 | dynamic linker is something other than
|
---|
| 68 | <filename class="libraryfile">ld-linux.so.2</filename>, substitute
|
---|
| 69 | <quote>ld-linux.so.2</quote> with the name of the platform's
|
---|
| 70 | dynamic linker in the above commands. Refer back to <xref
|
---|
| 71 | linkend="ch-tools-toolchaintechnotes" role=","/> if
|
---|
| 72 | necessary.</para></important>
|
---|
| 73 |
|
---|
[f3a70cd] | 74 | <beginpage/>
|
---|
| 75 |
|
---|
[81fd230] | 76 | <caution><para>It is imperative at this point to stop and ensure that
|
---|
| 77 | the basic functions (compiling and linking) of the adjusted toolchain
|
---|
| 78 | are working as expected. To do this, perform a sanity
|
---|
| 79 | check:</para>
|
---|
[673b0d8] | 80 |
|
---|
| 81 | <screen><userinput>echo 'main(){}' > dummy.c
|
---|
| 82 | cc dummy.c
|
---|
| 83 | readelf -l a.out | grep ': /lib'</userinput></screen>
|
---|
| 84 |
|
---|
[81fd230] | 85 | <para>If everything is working correctly, there should be no errors,
|
---|
| 86 | and the output of the last command will be (allowing for
|
---|
| 87 | platform-specific differences in dynamic linker name):</para>
|
---|
[673b0d8] | 88 |
|
---|
[8ad7980] | 89 | <screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
|
---|
[673b0d8] | 90 |
|
---|
[81fd230] | 91 | <para>Note that <filename class="directory">/lib</filename> is now
|
---|
| 92 | the prefix of our dynamic linker.</para>
|
---|
[673b0d8] | 93 |
|
---|
[81fd230] | 94 | <para>If the output does not appear as shown above or is not received
|
---|
| 95 | at all, then something is seriously wrong. Investigate and retrace the
|
---|
| 96 | steps to find out where the problem is and correct it. The most likely
|
---|
| 97 | reason is that something went wrong with the specs file amendment
|
---|
| 98 | above. Any issues will need to be resolved before continuing on with
|
---|
| 99 | the process.</para>
|
---|
[673b0d8] | 100 |
|
---|
[81fd230] | 101 | <para>Once everything is working correctly, clean up the test
|
---|
| 102 | files:</para>
|
---|
| 103 |
|
---|
| 104 | <screen><userinput>rm dummy.c a.out</userinput></screen></caution>
|
---|
[673b0d8] | 105 |
|
---|
| 106 | </sect1>
|
---|
[81fd230] | 107 |
|
---|