|
|
@@ -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>
|
Alex Gronenwoud