diff options
Diffstat (limited to 'chapter05/toolchaintechnotes.xml')
| -rw-r--r-- | chapter05/toolchaintechnotes.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml index 802e6cf4d..6524c3486 100644 --- a/chapter05/toolchaintechnotes.xml +++ b/chapter05/toolchaintechnotes.xml @@ -69,7 +69,7 @@ linker will be used</para></listitem> </itemizedlist> <para>Binutils is installed first because the -<command>./configure</command> runs of both GCC and Glibc perform +<command>configure</command> runs of both GCC and Glibc perform various feature tests on the assembler and linker to determine which software features to enable or disable. This is more important than one might first realize. An incorrectly configured GCC or Glibc can @@ -94,7 +94,7 @@ succeeded</userinput> will show all the files successfully opened during the linking.</para> <para>The next package installed is GCC. An example of what can be -seen during its run of <command>./configure</command> is:</para> +seen during its run of <command>configure</command> is:</para> <screen><computeroutput>checking what assembler to use... /tools/i686-pc-linux-gnu/bin/as @@ -123,7 +123,7 @@ will always use the <command>gcc</command> found in a The binary tools and kernel headers can be a bit more complicated. Therefore, take no risks and use the available configure switches to enforce the correct selections. After the run of -<command>./configure</command>, check the contents of the +<command>configure</command>, check the contents of the <filename>config.make</filename> file in the <filename class="directory">glibc-build</filename> directory for all important details. Note the use of <parameter>CC="gcc -B/tools/bin/"</parameter> |