Ignore:
Timestamp:
01/30/2006 06:51:33 AM (18 years ago)
Author:
Jeremy Huntwork <jhuntwork@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
16328ae
Parents:
62d3362
Message:

Various textual corrections. Thanks Chris Staub.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7317 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter06/binutils.xml

    r62d3362 r28bb0634  
    6060<screen><userinput>make tooldir=/usr</userinput></screen>
    6161
    62 <para>Normally, the tooldir (the directory where the executables will ultimately
    63 be located) is set to <filename
    64 class="directory">$(exec_prefix)/$(target_alias)</filename>. For example, i686
    65 machines would expand that to <filename
    66 class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is a custom
    67 system, this target-specific directory in <filename
    68 class="directory">/usr</filename> is not required. <filename
    69 class="directory">$(exec_prefix)/$(target_alias)</filename> would be used if the
    70 system was used to cross-compile (for example, compiling a package on an Intel
    71 machine that generates code that can be executed on PowerPC machines).</para>
     62  <variablelist>
     63    <title>The meaning of the make parameter:</title>
     64     <varlistentry>
     65      <term><parameter>tooldir=/usr</parameter></term>
     66      <listitem>
     67        <para>Normally, the tooldir (the directory where the executables will
     68        ultimately be located) is set to <filename
     69        class="directory">$(exec_prefix)/$(target_alias)</filename>. For
     70        example, i686 machines would expand that to <filename
     71        class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is
     72        a custom system, this target-specific directory in <filename
     73        class="directory">/usr</filename> is not required. <filename
     74        class="directory">$(exec_prefix)/$(target_alias)</filename> would be
     75        used if the system was used to cross-compile (for example, compiling a
     76        package on an Intel machine that generates code that can be executed
     77        on PowerPC machines).</para>
     78      </listitem>
     79    </varlistentry>
     80  </variablelist>
    7281
    7382<important><para>The test suite for Binutils in this section is
Note: See TracChangeset for help on using the changeset viewer.