diff options
Diffstat (limited to 'chapter06/binutils.xml')
| -rw-r--r-- | chapter06/binutils.xml | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml index 27b369b4e..e6ba783d8 100644 --- a/chapter06/binutils.xml +++ b/chapter06/binutils.xml @@ -68,15 +68,16 @@ cd ../binutils-build</userinput></screen> <screen><userinput>make tooldir=/usr</userinput></screen> -<para>Normally, the tooldir (the directory where the executables will -ultimately be located) is set to <filename -class="directory">$(exec_prefix)/$(target_alias)</filename>, which -expands into <filename class="directory">/usr/i686-pc-linux-gnu</filename>. -Because this is a custom system, this target-specific directory in <filename -class="directory">/usr</filename> is not required. This setup would be -used if the system was used to cross-compile (for example, compiling a -package on an Intel machine that generates code that can be executed -on PowerPC machines).</para> +<para>Normally, the tooldir (the directory where the executables will ultimately +be located) is set to <filename +class="directory">$(exec_prefix)/$(target_alias)</filename>. For example, i686 +machines would expand that to <filename +class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is a custom +system, this target-specific directory in <filename +class="directory">/usr</filename> is not required. <filename +class="directory">$(exec_prefix)/$(target_alias)</filename> would be used if the +system was used to cross-compile (for example, compiling a package on an Intel +machine that generates code that can be executed on PowerPC machines).</para> <important><para>The test suite for Binutils in this section is considered critical. Do not skip it under any |