Changeset f6ea270


Ignore:
Timestamp:
05/26/2002 08:48:08 PM (22 years ago)
Author:
Gerard Beekmans <gerard@…>
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.0, 6.1, 6.1.1, 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, v4_0, v4_1, v5_0, v5_1, v5_1_1, 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:
624fe951
Parents:
9ef92bb
Message:

removed tooldir from c5-binutils - not needed here, moved explanation to chap6

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

Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    r9ef92bb rf6ea270  
    2727
    2828</para></listitem>
     29
     30<listitem><para>May 26th, 2002 [gerard]: Chapter 05+06 - Binutils: Removed
     31the tooldir setting from chapter 05-binutils, moved its description to
     32chapter 06-binutils.</para></listitem>
    2933
    3034<listitem><para>May 26th, 2002 [gerard]: Chapter 05 - Gawk &amp; Findutils:

  • chapter05/binutils-exp.xml

    r9ef92bb rf6ea270  
    1515to the value -all-static causes binutils to be linked statically.</para>
    1616
    17 <para><userinput>tooldir=$LFS/usr:</userinput> Normally, the tooldir (the
    18 directory where the executables from binutils end up in) is set to
    19 $(exec_prefix)/$(target_alias) which expands into, for example,
    20 /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
    21 need this target specific directory in $LFS/usr. That setup would be used
    22 if the system was used to cross-compile (for example
    23 compiling a package on the Intel machine that generates code that can be
    24 executed on Apple PowerPC machines).</para>
    25 
    2617</sect2>
    2718

  • chapter05/binutils-inst.xml

    r9ef92bb rf6ea270  
    1515cd ../binutils-build &amp;&amp;
    1616../binutils-&binutils-version;/configure --prefix=$LFS/static --disable-nls &amp;&amp;
    17 make tooldir=$LFS/static LDFLAGS=-all-static &amp;&amp;
    18 make tooldir=$LFS/static install</userinput></screen></para>
     17make LDFLAGS=-all-static &amp;&amp;
     18make install</userinput></screen></para>
    1919
    2020</sect2>

  • chapter06/binutils-exp.xml

    r9ef92bb rf6ea270  
    11<sect2>
    22<title>Command explanations</title>
     3
     4<para><userinput>tooldir=/usr:</userinput> Normally, the tooldir (the
     5directory where the executables from binutils end up in) is set to
     6$(exec_prefix)/$(target_alias) which expands into, for example,
     7/usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
     8need this target specific directory in /usr. That setup would be used
     9if the system was used to cross-compile (for example
     10compiling a package on the Intel machine that generates code that can be
     11executed on Apple PowerPC machines).</para>
    312
    413<para><userinput>make tooldir=/usr install-info:</userinput> This will
Note: See TracChangeset for help on using the changeset viewer.