diff options
| -rw-r--r-- | chapter05/gcc-pass2-inst.xml | 14 | ||||
| -rw-r--r-- | chapter06/adjustingtoolchain.xml | 14 |
2 files changed, 16 insertions, 12 deletions
diff --git a/chapter05/gcc-pass2-inst.xml b/chapter05/gcc-pass2-inst.xml index 81a1b2dbf..b57ae3324 100644 --- a/chapter05/gcc-pass2-inst.xml +++ b/chapter05/gcc-pass2-inst.xml @@ -35,11 +35,15 @@ fixed headers from the host system, which would most likely not match the Glibc version actually used for the LFS system.</para> <para>The last patch changes GCC's default location of the dynamic linker -(typically ld-linux.so.2). It also removes <filename class="directory">/usr/include -</filename> from GCC's include search path. Patching now rather than adjusting -the specs file after installation ensures that our new dynamic linker gets used -during the actual build of GCC. That is, all the final (and temporary) binaries -created during the build will link against the new Glibc.</para> +(typically <filename>ld-linux.so.2</filename>). It also removes +<filename class="directory">/usr/include</filename> from GCC's include search +path. Patching now rather than adjusting the specs file after installation +ensures that our new dynamic linker gets used during the actual build of GCC. +That is, all the final (and temporary) binaries created during the build will +link against the new Glibc.</para> + +<important><para>These patches are <emphasis>critical</emphasis> in ensuring a +successful overall build. Do not forget to apply them.</para></important> <para>Create a separate build directory again:</para> diff --git a/chapter06/adjustingtoolchain.xml b/chapter06/adjustingtoolchain.xml index 55415a9e8..46be432b0 100644 --- a/chapter06/adjustingtoolchain.xml +++ b/chapter06/adjustingtoolchain.xml @@ -36,27 +36,27 @@ before, it is a good idea to check the specs file to ensure the intended changes were actually made.</para> <caution><para>It is imperative at this point to stop and ensure that the -basic functionality of the adjusted toolchain is working as expected. We are -going to perform a simple sanity check:</para> +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> <para><screen><userinput>echo 'main(){}' > dummy.c gcc dummy.c readelf -l a.out | grep ': /lib'</userinput></screen></para> -<para>If everything is working correctly, the output of the last command will -be:</para> +<para>If everything is working correctly, there should be no errors, and the +output of the last command will be:</para> <para><screen>[Requesting program interpreter: /lib/ld-linux.so.2] </screen></para> -<para>If you did not receive the output as shown above then something is +<para>If you did not receive the output as shown above, then something is seriously wrong. You will need to investigate and retrace your steps to find out where the problem is and correct it. There is no point in continuing -until this is done. Most likely, something went wrong with the specs file +until this is done. Most likely something went wrong with the specs file amendment above. Note especially that <filename>/lib</filename> now appears as the prefix of our dynamic linker. Of course, if you are working on a platform where the name of the dynamic linker is something other than <filename> -ld-linux.so.2</filename> then the output will be slightly different.</para> +ld-linux.so.2</filename>, then the output will be slightly different.</para> <para>Once you are satisfied that all is well, clean up the test files:</para> |