|
@@ -9,14 +9,14 @@
|
|
|
|
|
|
<para>Now that the temporary C libraries have been installed, all
|
|
|
the tools compiled in the rest of this chapter should be linked against these
|
|
|
-libraries. In order to accomplish this the linker, and the compiler's
|
|
|
+libraries. In order to accomplish this, the linker and the compiler's
|
|
|
specs file, need to be adjsted.</para>
|
|
|
|
|
|
<para> Some people would say that there is <emphasis><quote>black magic juju
|
|
|
below this line</quote></emphasis>, but it is really very simple.</para>
|
|
|
|
|
|
-<para>First the adjusted linker is installed (adjusted at the end of the first pass
|
|
|
-of Binutils), by running the following command from within
|
|
|
+<para>First, the linker, adjusted at the end of the first pass of Binutils, is
|
|
|
+installed by running the following command from within
|
|
|
the <filename class="directory">binutils-build</filename> directory:</para>
|
|
|
|
|
|
<screen><userinput>make -C ld install</userinput></screen>
|
|
@@ -45,7 +45,11 @@ sed 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
|
|
|
mv -f tempspecfile $SPECFILE &&
|
|
|
unset SPECFILE</userinput></screen>
|
|
|
|
|
|
-<para>It is recommended that the above command be cut-and-pasted in order to ensure correctness - Alternatively the specs file can be edited by hand. This is done simply by replacing every occurrence of <quote>/lib/ld-linux.so.2</quote> with <quote>/tools/lib/ld-linux.so.2</quote>.</para>
|
|
|
+<para>It is recommended that the above command be cut-and-pasted in order to
|
|
|
+ensure correctness - Alternatively, the specs file can be edited by hand. This
|
|
|
+is done simply by replacing every occurrence of
|
|
|
+<quote>/lib/ld-linux.so.2</quote> with <quote>/tools/lib/ld-linux.so.2</quote>.
|
|
|
+</para>
|
|
|
|
|
|
<para> Be sure to visually inspect the specs file in order to verify the intended changes have been made.</para>
|
|
|
|
|
@@ -66,7 +70,7 @@ Run the following commands to eliminate this possibility:</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.
|
|
|
-To perform a simple sanity check run the following commands:</para>
|
|
|
+To perform a simple sanity check, run the following commands:</para>
|
|
|
|
|
|
<screen><userinput>echo 'main(){}' > dummy.c
|
|
|
cc dummy.c
|
|
@@ -85,7 +89,7 @@ as shown above, or there was no output at all, 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.
|
|
|
First, perform the sanity check again, using <command>gcc</command> instead of
|
|
|
-<command>cc</command>. If this works then the
|
|
|
+<command>cc</command>. If this works, then the
|
|
|
<filename class="symlink">/tools/bin/cc</filename> symlink is missing. Revisit
|
|
|
<xref linkend="ch-tools-gcc-pass1"/> and install the symlink. Second, ensure your PATH
|
|
|
is correct. You can check this by running <userinput>echo $PATH</userinput> and
|