[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-tools-adjusting">
|
---|
[bce08ef] | 7 | <title>Adjusting the Toolchain</title>
|
---|
[673b0d8] | 8 | <?dbhtml filename="adjusting.html"?>
|
---|
| 9 |
|
---|
[81fd230] | 10 | <para>Now that the temporary C libraries have been installed, all
|
---|
| 11 | tools compiled in the rest of this chapter should be linked against
|
---|
| 12 | these libraries. In order to accomplish this, the linker and the
|
---|
| 13 | compiler's specs file need to be adjusted.</para>
|
---|
| 14 |
|
---|
| 15 | <para>The linker, adjusted at the end of the first pass of Binutils,
|
---|
| 16 | is installed by running the following command from within the
|
---|
| 17 | <filename class="directory">binutils-build</filename> directory:</para>
|
---|
[673b0d8] | 18 |
|
---|
| 19 | <screen><userinput>make -C ld install</userinput></screen>
|
---|
| 20 |
|
---|
[81fd230] | 21 | <para>From this point onwards, everything will link only
|
---|
| 22 | against the libraries in <filename class="directory">/tools/lib</filename>.</para>
|
---|
| 23 |
|
---|
| 24 | <note><para>If the earlier warning to retain the Binutils source and
|
---|
| 25 | build directories from the first pass was missed, ignore the above
|
---|
| 26 | command. This results in a small chance that the subsequent testing
|
---|
| 27 | programs will link against libraries on the host. This is not ideal,
|
---|
| 28 | but it is not a major problem. The situation is corrected when the
|
---|
| 29 | second pass of Binutils is installed later.</para></note>
|
---|
| 30 |
|
---|
| 31 | <para>Now that the adjusted linker is installed, the Binutils build and source
|
---|
| 32 | directories should be removed.</para>
|
---|
| 33 |
|
---|
| 34 | <para>The next task is to amend the GCC specs file so that it points
|
---|
| 35 | to the new dynamic linker. A simple sed script will accomplish this:</para>
|
---|
| 36 |
|
---|
| 37 | <!-- Ampersands are needed to allow copy and paste -->
|
---|
[673b0d8] | 38 |
|
---|
[9109cd4] | 39 | <screen><userinput>SPECFILE=`gcc --print-file specs` &&
|
---|
[2ec4b60] | 40 | sed 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
|
---|
[673b0d8] | 41 | $SPECFILE > tempspecfile &&
|
---|
| 42 | mv -f tempspecfile $SPECFILE &&
|
---|
| 43 | unset SPECFILE</userinput></screen>
|
---|
| 44 |
|
---|
[5dd601f] | 45 | <para><phrase condition="html">It is recommended that the above
|
---|
| 46 | command be copy-and-pasted in order to ensure accuracy.</phrase>
|
---|
[81fd230] | 47 | Alternatively, the specs file can be edited by hand. This is done by
|
---|
| 48 | replacing every occurrence of <quote>/lib/ld-linux.so.2</quote> with
|
---|
| 49 | <quote>/tools/lib/ld-linux.so.2</quote></para>
|
---|
| 50 |
|
---|
| 51 | <para>Be sure to visually inspect the specs file in order to verify the
|
---|
| 52 | intended changes have been made.</para>
|
---|
| 53 |
|
---|
| 54 | <important><para>If working on a platform where the name of the
|
---|
| 55 | dynamic linker is something other than
|
---|
| 56 | <filename class="libraryfile">ld-linux.so.2</filename>, replace
|
---|
| 57 | <quote>ld-linux.so.2</quote> with the name of the platform's
|
---|
| 58 | dynamic linker in the above commands. Refer back to <xref
|
---|
| 59 | linkend="ch-tools-toolchaintechnotes" role=","/> if
|
---|
| 60 | necessary.</para></important>
|
---|
| 61 |
|
---|
| 62 | <para>There is a possibility that some include files from the host
|
---|
| 63 | system have found their way into GCC's private include dir. This can
|
---|
| 64 | happen as a result of GCC's <quote>fixincludes</quote> process, which runs as part
|
---|
| 65 | of the GCC build. This is explained in more detail later in this
|
---|
| 66 | chapter. Run the following command to eliminate this
|
---|
| 67 | possibility:</para>
|
---|
[3d36131c] | 68 |
|
---|
[c8ba565] | 69 | <screen><userinput>rm -f /tools/lib/gcc/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>
|
---|
[673b0d8] | 70 |
|
---|
[0b5096ca] | 71 | <beginpage/>
|
---|
| 72 |
|
---|
[81fd230] | 73 | <caution><para>At this point, it is imperative to stop and ensure that
|
---|
| 74 | the basic functions (compiling and linking) of the new toolchain are
|
---|
| 75 | working as expected. To perform a sanity check, run the following
|
---|
| 76 | commands:</para>
|
---|
[fba1478] | 77 |
|
---|
[673b0d8] | 78 | <screen><userinput>echo 'main(){}' > dummy.c
|
---|
| 79 | cc dummy.c
|
---|
| 80 | readelf -l a.out | grep ': /tools'</userinput></screen>
|
---|
| 81 |
|
---|
[81fd230] | 82 | <para>If everything is working correctly, there should be no errors,
|
---|
| 83 | and the output of the last command will be of the form:</para>
|
---|
[673b0d8] | 84 |
|
---|
[d72e04a] | 85 | <screen><computeroutput>[Requesting program interpreter:
|
---|
| 86 | /tools/lib/ld-linux.so.2]</computeroutput></screen>
|
---|
[673b0d8] | 87 |
|
---|
[81fd230] | 88 | <para>Note that <filename class="directory">/tools/lib</filename>
|
---|
| 89 | appears as the prefix of the dynamic linker.</para>
|
---|
[3d36131c] | 90 |
|
---|
[81fd230] | 91 | <para>If the output is not shown as above or there was no output at
|
---|
| 92 | all, then something is wrong. Investigate and retrace the steps to
|
---|
| 93 | find out where the problem is and correct it. This issue must be
|
---|
| 94 | resolved before continuing on. First, perform the sanity check again,
|
---|
| 95 | using <command>gcc</command> instead of <command>cc</command>. If this
|
---|
| 96 | works, then the <filename class="symlink">/tools/bin/cc</filename> symlink is missing.
|
---|
| 97 | Revisit <xref linkend="ch-tools-gcc-pass1" role=","/> and install the symlink.
|
---|
| 98 | Next, ensure that the <envar>PATH</envar> is correct. This can be checked by running
|
---|
| 99 | <command>echo $PATH</command> and verifying that <filename
|
---|
| 100 | class="directory">/tools/bin</filename> is at the head of the list. If
|
---|
| 101 | the <envar>PATH</envar> is wrong it could mean that you are not logged in as user
|
---|
| 102 | <emphasis>lfs</emphasis> or that something went wrong back in <xref
|
---|
| 103 | linkend="ch-tools-settingenviron" role="."/> Another option is that something
|
---|
| 104 | may have gone wrong with the specs file amendment above. In this case,
|
---|
[5dd601f] | 105 | redo the specs file amendment<phrase condition="html">, being careful to copy-and-paste the
|
---|
| 106 | commands</phrase>.</para>
|
---|
[673b0d8] | 107 |
|
---|
[81fd230] | 108 | <para>Once all is well, clean up the test files:</para>
|
---|
| 109 |
|
---|
| 110 | <screen><userinput>rm dummy.c a.out</userinput></screen>
|
---|
| 111 | </caution>
|
---|
[673b0d8] | 112 |
|
---|
| 113 | </sect1>
|
---|
[81fd230] | 114 |
|
---|