diff options
Diffstat (limited to 'chapter05/chapter05.xml')
-rw-r--r-- | chapter05/chapter05.xml | 24 |
1 files changed, 11 insertions, 13 deletions
diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index 8e5699990..870c02ba6 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -439,23 +439,24 @@ temporary tools, source the just-created profile:</para> &c5-glibc; -<sect1 id="ch-tools-locking-glibc"> -<title>"Locking in" Glibc</title> -<?dbhtml filename="lockingglibc.html" dir="chapter05"?> +<sect1 id="ch-tools-adjusting"> +<title>Adjusting the toolchain</title> +<?dbhtml filename="adjusting.html" dir="chapter05"?> <para>Now that the temporary C libraries have been installed, we want all the tools compiled in the rest of this chapter to be linked against these libraries. To accomplish this, we need to adjust the linker and the compiler's -specs file.</para> +specs file. Some people would say that it is <emphasis>"black magic juju below +this line"</emphasis>, but it is really very simple.</para> -<para>First install the adjusted linker by running the following from within +<para>First install the adjusted linker (adjusted at the end of the first pass +of Binutils) by running the following command from within the <filename class="directory">binutils-build</filename> directory:</para> <screen><userinput>make -C ld install</userinput></screen> -<para>The linker was adjusted a little while back, at the end of the first -pass of Binutils. From this point onwards everything will link <emphasis>only -</emphasis> against the libraries in <filename>/tools/lib</filename>.</para> +<para>From this point onwards everything will link <emphasis>only</emphasis> +against the libraries in <filename>/tools/lib</filename>.</para> <note><para>If you somehow missed the earlier warning to retain the Binutils source and build directories from the first pass or otherwise accidentally @@ -465,8 +466,8 @@ testing programs linking against libraries on the host. This is not ideal, but it's not a major problem. The situation is corrected when we install the second pass of Binutils a bit further on.</para></note> -<para>Now that the adjusted linker is installed, you have to remove the -Binutils build and source directories.</para> +<para>Now that the adjusted linker is installed, you have to +<emphasis>remove</emphasis> the Binutils build and source directories.</para> <para>The next thing to do is to amend our GCC specs file so that it points to the new dynamic linker. A simple sed will accomplish this:</para> @@ -541,9 +542,6 @@ ensuring to cut-and-paste the commands as was recommended.</para> <!-- HACK - Force some whitespace to appease tidy --> <literallayout></literallayout> -<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> |