diff options
Diffstat (limited to 'chapter06/adjustingtoolchain.xml')
| -rw-r--r-- | chapter06/adjustingtoolchain.xml | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/chapter06/adjustingtoolchain.xml b/chapter06/adjustingtoolchain.xml index b033a8d3f..ba61d857a 100644 --- a/chapter06/adjustingtoolchain.xml +++ b/chapter06/adjustingtoolchain.xml @@ -17,8 +17,8 @@ adjusted linker by running the following from within the <note><para>If you somehow missed the earlier warning to retain the Binutils source and build directories from the second pass in Chapter 5 or otherwise accidentally deleted them or just don't have access to them, don't worry, all is -not lost. Just ignore this step. The result will be that the next package, -Binutils, will link against the Glibc libraries in +not lost. Just ignore the above command. The result will be that the next +package, Binutils, will link against the Glibc libraries in <filename class="directory">/tools</filename> rather than <filename class="directory">/usr</filename>. This is not ideal, however, our testing has shown that the resulting Binutils program binaries should be @@ -41,8 +41,7 @@ to the new dynamic linker. Just like earlier on, we use a sed to accomplish this:</para> <para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs -sed -e 's@/tools/lib/ld.so.1@/lib/ld.so.1@g' \ - -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \ +sed -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \ $SPECFILE > newspecfile mv newspecfile $SPECFILE unset SPECFILE</userinput></screen></para> @@ -51,6 +50,12 @@ unset SPECFILE</userinput></screen></para> before, it is a good idea to check the specs file to ensure the intended changes were actually made.</para> +<important><para>If you are working on a platform where the name of the dynamic +linker is something other than <filename>ld-linux.so.2</filename>, you +<emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the +name of your platform's dynamic linker in the above commands. Refer back to the +"Toolchain technical notes" section if necessary.</para></important> + <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. For this we are going to perform a simple sanity check:</para> |