diff options
| author | Alex Gronenwoud <alex@linuxfromscratch.org> | 2003-09-17 22:00:04 +0000 |
|---|---|---|
| committer | Alex Gronenwoud <alex@linuxfromscratch.org> | 2003-09-17 22:00:04 +0000 |
| commit | 783c04114968cf7d9cc16345d881631d6b5686b6 (patch) | |
| tree | 6c8401920a6ef6ea01d1905966fdadd4b46a3f7b | |
| parent | 552a690b44b664960a18e070f271995f05fca63f (diff) | |
Minor adjustments to the 'Lock-in' section.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2834 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
| -rw-r--r-- | chapter05/lockingglibc.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/chapter05/lockingglibc.xml b/chapter05/lockingglibc.xml index e2214119e..2851750a7 100644 --- a/chapter05/lockingglibc.xml +++ b/chapter05/lockingglibc.xml @@ -38,32 +38,32 @@ all in. Or you can edit the specs file by hand if you want to: just replace system have found their way into GCC's private include dir. This can happen because of GCC's "fixincludes" process which runs as part of the GCC build. We'll explain more about this further on in this chapter. For now, run the -following commands to eliminate this possibility.</para> +following commands to eliminate this possibility:</para> <para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para> -<caution><para>It is imperative at this point to stop and ensure that the -basic functionality of the new toolchain is working as expected. We are going -to perform a simple sanity check:</para> +<caution><para>It is imperative at this point to stop and ensure that the basic +functions (compiling and linking) of the new 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 ': /tools'</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: /tools/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>/tools/lib</filename> 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. +<filename>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> @@ -71,7 +71,7 @@ platform where the name of the dynamic linker is something other than <para><screen><userinput>rm dummy.c a.out</userinput></screen></para> </caution> -<para>This completes the installation of the self-contained toolchain, which +<para>This completes the installation of the self-contained toolchain, and it can now be used to build the rest of the temporary tools.</para> </sect1> |