Changeset ae581da


Ignore:
Timestamp:
08/28/2003 09:19:09 PM (21 years ago)
Author:
Alex Gronenwoud <alex@…>
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, 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:
2ab760c
Parents:
871df54
Message:

Updating chapter 6 Binutils and Gcc installation text.

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

Location:
chapter06
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • chapter06/binutils-inst.xml

    r871df54 rae581da  
    77Therefore, if you have defined any environment variables that override
    88default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
    9 or modifying them when building binutils.</para>
     9or modifying them when building Binutils.</para>
    1010
    1111<para>It is recommended by the Binutils installation documentation to build
    … …  
    1515cd ../binutils-build</userinput></screen></para>
    1616
    17 <para>Next, prepare Binutils to be compiled:</para>
     17<para>Now prepare Binutils for compilation:</para>
    1818
    1919<para><screen><userinput>../binutils-&binutils-version;/configure \
    2020&nbsp;&nbsp;&nbsp;&nbsp;--prefix=/usr --enable-shared</userinput></screen></para>
    2121
    22 <para>Continue with compiling the package:</para>
     22<para>Compile the package:</para>
    2323
    2424<para><screen><userinput>make tooldir=/usr</userinput></screen></para>
    2525
     26<para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
     27executables end up) is set to $(exec_prefix)/$(target_alias), which expands
     28into, for example, <filename>/usr/i686-pc-linux-gnu</filename>. Since we only
     29build for our own system, we don't need this target specific directory in
     30<filename>/usr</filename>. That setup would be used if the system was used to
     31cross-compile (for example compiling a package on an Intel machine that
     32generates code that can be executed on PowerPC machines).</para>
     33
     34<para>Check the results:</para>
     35
    2636<para><screen><userinput>make check</userinput></screen></para>
    27 
    28 <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
    29 executables end up) is set to $(exec_prefix)/$(target_alias) which expands
    30 into, for example, /usr/i686-pc-linux-gnu. Since we only build for our
    31 own system, we don't need this target specific directory in /usr. That
    32 setup would be used if the system was used to cross-compile (for example
    33 compiling a package on the Intel machine that generates code that can be
    34 executed on Apple PowerPC machines).</para>
    3537
    3638<para>Install the package:</para>
    … …  
    3840<para><screen><userinput>make tooldir=/usr install</userinput></screen></para>
    3941
     42<para>And remove a library that normally is not meant to be installed on its
     43own:</para>
     44
    4045<para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para>
    4146

  • chapter06/gcc-inst.xml

    r871df54 rae581da  
    1010or modifying them when building GCC.</para>
    1111
    12 <para>We will be building the C and C++ compilers at this time, so you'll
    13 need to unpack both the gcc-core and gcc-g++ tarballs. Other compilers are
    14 available in the full gcc package; instructions for building them may be
    15 found at <ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para>
     12<para>This time we will build both the C and the C++ compiler, so you'll have
     13to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
     14will unfold into the same directory. The full GCC package contains even more
     15compilers. Instructions for building these can be found at
     16<ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para>
    1617
    1718<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch
    1819patch -Np1 -i ../gcc-&gcc-version;-mmap_test.patch</userinput></screen></para>
    1920
    20 <para>It is recommended by the GCC installation documentation to build GCC
    21 in a dedicated directory outside of the source tree. Create the build
    22 directory:</para>
     21<para>GCC's installation documentation recommends to build the package in a
     22dedicated directory separate from the source tree. Create this build
     23directory and go there:</para>
    2324
    2425<para><screen><userinput>mkdir ../gcc-build
    2526cd ../gcc-build</userinput></screen></para>
    2627
    27 <para>Prepare GCC to be compiled:</para>
     28<para>Now prepare GCC for compilation:</para>
    2829
    2930<para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
    … …  
    3233&nbsp;&nbsp;&nbsp;&nbsp;--enable-languages=c,c++</userinput></screen></para>
    3334
    34 <para>The meanings of the configure options are:</para>
     35<para>The meaning of the new configure options:</para>
    3536
    3637<itemizedlist>
    … …  
    5152</itemizedlist>
    5253
    53 <para>Continue with compiling the package:</para>
     54<para>Compile the package:</para>
    5455
    5556<para><screen><userinput>make</userinput></screen></para>
    5657
     58<para>Check the results, but don't stop at errors (you'll remember the few
     59known ones):</para>
     60
    5761<para><screen><userinput>make -k check</userinput></screen></para>
    5862
    59 <para>Finish installing the package:</para>
     63<para>And install the package:</para>
    6064
    6165<para><screen><userinput>make install</userinput></screen></para>
    … …  
    6771<para><screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen></para>
    6872
    69 <para>Many packages compile using <emphasis>cc</emphasis> as the name for
    70 the C compiler. To satisfy those packages, create a <emphasis>cc</emphasis>
    71 symlink:</para>
     73<para>Many packages use the name <userinput>cc</userinput> to call the C
     74compiler. To satisfy those packages, create a symlink:</para>
    7275
    7376<para><screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen></para>
     77
     78<para>Remove the spurious a-out library again:</para>
    7479
    7580<para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para>
Note: See TracChangeset for help on using the changeset viewer.