[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[b06ca36] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
[673b0d8] | 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
[81109e3] | 7 |
|
---|
[673b0d8] | 8 | <sect1 id="ch-tools-adjusting">
|
---|
[81109e3] | 9 | <?dbhtml filename="adjusting.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Adjusting the Toolchain</title>
|
---|
[673b0d8] | 12 |
|
---|
[81109e3] | 13 | <para>Now that the temporary C libraries have been installed, all
|
---|
| 14 | tools compiled in the rest of this chapter should be linked against
|
---|
| 15 | these libraries. In order to accomplish this, the linker and the
|
---|
| 16 | compiler's specs file need to be adjusted.</para>
|
---|
[81fd230] | 17 |
|
---|
[62d3362] | 18 | <para>The linker, adjusted at the end of the first pass of Binutils, needs
|
---|
| 19 | to be renamed so that it can be properly found and used. First, backup the
|
---|
| 20 | original linker, then replace it with the adjusted linker. We'll also
|
---|
| 21 | create a link to its counterpart in <filename class="directory">
|
---|
[f19e766] | 22 | /tools/$(gcc -dumpmachine)/bin</filename>:</para>
|
---|
[673b0d8] | 23 |
|
---|
[62d3362] | 24 | <screen><userinput>mv -v /tools/bin/{ld,ld-old}
|
---|
| 25 | mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
|
---|
| 26 | mv -v /tools/bin/{ld-new,ld}
|
---|
| 27 | ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld</userinput></screen>
|
---|
[673b0d8] | 28 |
|
---|
[81109e3] | 29 | <para>From this point onwards, everything will link only against the
|
---|
| 30 | libraries in <filename class="directory">/tools/lib</filename>.</para>
|
---|
[81fd230] | 31 |
|
---|
[81109e3] | 32 | <para>The next task is to point GCC to the new dynamic linker. This is done by
|
---|
| 33 | dumping GCC's <quote>specs</quote> file to a location where GCC will look for it
|
---|
| 34 | by default. A simple <command>sed</command> substitution then alters the
|
---|
[19f8a62] | 35 | dynamic linker that GCC will use.</para>
|
---|
[81fd230] | 36 |
|
---|
[19f8a62] | 37 | <para>For the sake of accuracy, it is recommended to use a copy-and-paste
|
---|
| 38 | method when issuing the following command. Be sure to visually inspect the
|
---|
| 39 | specs file and verify that all occurrences of <quote>/lib/ld-linux.so.2</quote>
|
---|
[f19e766] | 40 | have been replaced with <quote>/tools/lib/ld-linux.so.2</quote>:</para>
|
---|
[81109e3] | 41 |
|
---|
| 42 | <important>
|
---|
| 43 | <para>If working on a platform where the name of the dynamic linker is
|
---|
| 44 | something other than <filename class="libraryfile">ld-linux.so.2</filename>,
|
---|
| 45 | replace <quote>ld-linux.so.2</quote> with the name of the platform's
|
---|
[09ec1f4] | 46 | dynamic linker in the following commands. Refer to <xref
|
---|
[81109e3] | 47 | linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para>
|
---|
| 48 | </important>
|
---|
| 49 |
|
---|
[19f8a62] | 50 | <!-- Ampersands are needed to allow copy and paste -->
|
---|
[b0a4c9a] | 51 | <screen><userinput>gcc -dumpspecs | sed 's@/lib/ld-linux.so.2@/tools&@g' \
|
---|
[19f8a62] | 52 | > `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
|
---|
| 53 |
|
---|
[81109e3] | 54 | <para>During the build process, GCC runs a script
|
---|
| 55 | (<command>fixincludes</command>) that scans the system for header files
|
---|
| 56 | that may need to be fixed (they might contain syntax errors, for example),
|
---|
| 57 | and installs the fixed versions in a private include directory. There is a
|
---|
| 58 | possibility that, as a result of this process, some header files from the
|
---|
| 59 | host system have found their way into GCC's private include directory. As
|
---|
| 60 | the rest of this chapter only requires the headers from GCC and Glibc,
|
---|
| 61 | which have both been installed at this point, any <quote>fixed</quote>
|
---|
| 62 | headers can safely be removed. This helps to avoid any host headers
|
---|
| 63 | polluting the build environment. Run the following commands to remove the
|
---|
| 64 | header files in GCC's private include directory (you may find it easier to
|
---|
| 65 | copy and paste these commands, rather than typing them by hand, due to
|
---|
| 66 | their length):</para>
|
---|
[3d36131c] | 67 |
|
---|
[2e02c35] | 68 | <!-- && used to ease copy and pasting -->
|
---|
[25a4471] | 69 | <screen><userinput>GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include &&
|
---|
| 70 | find ${GCC_INCLUDEDIR}/* -maxdepth 0 -xtype d -exec rm -rvf '{}' \; &&
|
---|
| 71 | rm -vf `grep -l "DO NOT EDIT THIS FILE" ${GCC_INCLUDEDIR}/*` &&
|
---|
[2e02c35] | 72 | unset GCC_INCLUDEDIR</userinput></screen>
|
---|
[673b0d8] | 73 |
|
---|
[81109e3] | 74 | <caution>
|
---|
| 75 | <para>At this point, it is imperative to stop and ensure that the basic
|
---|
| 76 | functions (compiling and linking) of the new toolchain are working as
|
---|
| 77 | expected. To perform a sanity check, run the following commands:</para>
|
---|
[fba1478] | 78 |
|
---|
[673b0d8] | 79 | <screen><userinput>echo 'main(){}' > dummy.c
|
---|
| 80 | cc dummy.c
|
---|
| 81 | readelf -l a.out | grep ': /tools'</userinput></screen>
|
---|
| 82 |
|
---|
[81109e3] | 83 | <para>If everything is working correctly, there should be no errors,
|
---|
| 84 | and the output of the last command will be of the form:</para>
|
---|
[673b0d8] | 85 |
|
---|
[81109e3] | 86 | <screen><computeroutput>[Requesting program interpreter:
|
---|
[d72e04a] | 87 | /tools/lib/ld-linux.so.2]</computeroutput></screen>
|
---|
[673b0d8] | 88 |
|
---|
[81109e3] | 89 | <para>Note that <filename class="directory">/tools/lib</filename>
|
---|
| 90 | appears as the prefix of the dynamic linker.</para>
|
---|
| 91 |
|
---|
| 92 | <para>If the output is not shown as above or there was no output at all,
|
---|
| 93 | then something is wrong. Investigate and retrace the steps to find out
|
---|
| 94 | where the problem is and correct it. This issue must be resolved before
|
---|
| 95 | continuing on. First, perform the sanity check again, using
|
---|
| 96 | <command>gcc</command> instead of <command>cc</command>. If this works,
|
---|
| 97 | then the <filename class="symlink">/tools/bin/cc</filename> symlink is
|
---|
| 98 | missing. Revisit <xref linkend="ch-tools-gcc-pass1" role=","/> and install
|
---|
| 99 | the symlink. Next, ensure that the <envar>PATH</envar> is correct. This
|
---|
| 100 | can be checked by running <command>echo $PATH</command> and verifying that
|
---|
| 101 | <filename class="directory">/tools/bin</filename> is at the head of the
|
---|
| 102 | list. If the <envar>PATH</envar> is wrong it could mean that you are not
|
---|
| 103 | logged in as user <systemitem class="username">lfs</systemitem> or that
|
---|
| 104 | something went wrong back in <xref linkend="ch-tools-settingenviron"
|
---|
| 105 | role="."/> Another option is that something may have gone wrong with the
|
---|
| 106 | specs file amendment above. In this case, redo the specs file amendment,
|
---|
| 107 | being careful to copy-and-paste the commands.</para>
|
---|
| 108 |
|
---|
| 109 | <para>Once all is well, clean up the test files:</para>
|
---|
[81fd230] | 110 |
|
---|
[5998892] | 111 | <screen><userinput>rm -v dummy.c a.out</userinput></screen>
|
---|
[05d80ab8] | 112 |
|
---|
[81109e3] | 113 | </caution>
|
---|
[673b0d8] | 114 |
|
---|
[1129dbd] | 115 | <note><para>Building Tcl in the next section will serve as an additional check that
|
---|
| 116 | the toolchain has been built properly. If Tcl fails to build, it is an
|
---|
[9b41802] | 117 | indication that something has gone wrong with the Binutils, GCC, or Glibc
|
---|
[1129dbd] | 118 | installation, but not with Tcl itself.</para></note>
|
---|
[9b41802] | 119 |
|
---|
[673b0d8] | 120 | </sect1>
|
---|