Changeset 677aef3


Ignore:
Timestamp:
09/22/2003 02:25:37 PM (21 years ago)
Author:
Greg Schafer <greg@…>
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:
f4231a2
Parents:
3aa9774
Message:

GCC 2.95.3 fixes and other misc. toolchain related textual adjustments.

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

Files:
10 edited

Legend:

Unmodified
Added
Removed
  • chapter04/chapter04.xml

    r3aa9774 r677aef3  
    252252<ulink url="&http;/gawk-&gawk-patch-version;.patch"/>
    253253
    254 GCC Patch (&gcc-2953-patch-version;) - &gcc-2953-patch-size;:
     254GCC-2 Patch (&gcc-2953-patch-version;) - &gcc-2953-patch-size;:
    255255<ulink url="&http;/gcc-&gcc-2953-patch-version;.patch"/>
    256 
    257 GCC-2 Return-type Patch:
    258 <ulink url="&http;/gcc-2.95.3-returntype-fix.patch"/>
     256GCC-2 No Fixincludes Patch (&gcc-2953-no-fixinc-patch-version;) - &gcc-2953-no-fixinc-patch-size;:
     257<ulink url="&http;/gcc-&gcc-2953-no-fixinc-patch-version;-no-fixinc.patch"/>
     258GCC-2 Return Type Patch (&gcc-2953-returntype-fix-patch-version;) - &gcc-2953-returntype-fix-patch-size;:
     259<ulink url="&http;/gcc-&gcc-2953-returntype-fix-patch-version;-returntype-fix.patch"/>
    259260
    260261GCC No Fixincludes Patch:
  • chapter05/binutils-pass1-inst.xml

    r3aa9774 r677aef3  
    1919modifying them when building Binutils.</para>
    2020
    21 <para>It is recommended by the Binutils installation documentation to build
    22 Binutils outside of the source directory in a dedicated directory:</para>
     21<para>The Binutils documentation recommends building Binutils outside of the
     22source directory in a dedicated build directory:</para>
    2323
    2424<para><screen><userinput>mkdir ../binutils-build
  • chapter05/binutils-pass2-inst.xml

    r3aa9774 r677aef3  
    88</note>
    99
    10 <para>First create a separate build directory again:</para>
     10<para>Create a separate build directory again:</para>
    1111
    1212<para><screen><userinput>mkdir ../binutils-build
  • chapter05/gcc-pass1-inst.xml

    r3aa9774 r677aef3  
    1818or modifying them when building GCC.</para>
    1919
    20 <para>It is recommended by the GCC installation documentation to build
    21 GCC outside of the source directory in a dedicated directory:</para>
     20<para>The GCC documentation recommends building GCC outside of the source
     21directory in a dedicated build directory:</para>
    2222
    2323<para><screen><userinput>mkdir ../gcc-build
  • chapter05/glibc-inst.xml

    r3aa9774 r677aef3  
    3535</userinput></screen></para>
    3636
    37 <para>The documentation that comes with Glibc recommends to build the package
    38 not in the source directory but in a separate, dedicated directory:</para>
     37<para>The Glibc documentation recommends building Glibc outside of the source
     38directory in a dedicated build directory:</para>
    3939
    4040<para><screen><userinput>mkdir ../glibc-build
  • chapter06/binutils-inst.xml

    r3aa9774 r677aef3  
    1313or modifying them when building Binutils.</para>
    1414
    15 <para>It is recommended by the Binutils installation documentation to build
    16 Binutils outside of the source directory:</para>
     15<para>The Binutils documentation recommends building Binutils outside of the
     16source directory in a dedicated build directory:</para>
    1717
    1818<para><screen><userinput>mkdir ../binutils-build
  • chapter06/gcc-2953-inst.xml

    r3aa9774 r677aef3  
    1717developer's advice and using the version here to compile your kernel.</para>
    1818
     19<note><para>We don't install the C++ compiler or libraries here. However, there
     20may be reasons why you would want to install them. More information can be found
     21at <ulink url="&blfs-root;view/cvs/general/gcc2.html"/>.</para></note>
     22
    1923<para>We'll install this older release of GCC into the non-standard prefix of
    2024<filename class="directory">/opt</filename> so as to avoid interfering with
     
    2226 .</para>
    2327
    24 <para><screen><userinput>patch -Np1 -i ../gcc-2.95.3-2.patch
    25 patch -Np1 -i ../gcc-2.95.3-returntype-fix.patch
    26 echo timestamp > gcc/cstamp-h.in
    27 mkdir ../gcc-2-build
    28 cd ../gcc-2-build
    29 ../gcc-2.95.3/configure --prefix=/opt/gcc-2.95.3 \
     28<para>Apply the patches and make a small adjustment:</para>
     29
     30<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-2953-patch-version;.patch
     31patch -Np1 -i ../gcc-&gcc-2953-no-fixinc-patch-version;-no-fixinc.patch
     32patch -Np1 -i ../gcc-&gcc-2953-returntype-fix-patch-version;-returntype-fix.patch
     33echo timestamp > gcc/cstamp-h.in</userinput></screen></para>
     34
     35<para>The GCC documentation recommends building GCC outside of the source
     36directory in a dedicated build directory:</para>
     37
     38<para><screen><userinput>mkdir ../gcc-2-build
     39cd ../gcc-2-build</userinput></screen></para>
     40
     41<para>Compile and install gcc:</para>
     42
     43<para><screen><userinput>../gcc-2.95.3/configure --prefix=/opt/gcc-2.95.3 \
    3044&nbsp;&nbsp;&nbsp;&nbsp;--enable-shared --enable-languages=c \
    3145&nbsp;&nbsp;&nbsp;&nbsp;--enable-threads=posix
  • chapter06/gcc-inst.xml

    r3aa9774 r677aef3  
    2626as we will use the one provided by binutils instead.</para>
    2727
    28 <para>GCC's installation documentation recommends to build the package in a
    29 dedicated directory separate from the source tree. Create this build
    30 directory and go there:</para>
     28<para>The GCC documentation recommends building GCC outside of the source
     29directory in a dedicated build directory:</para>
    3130
    3231<para><screen><userinput>mkdir ../gcc-build
  • chapter06/glibc-inst.xml

    r3aa9774 r677aef3  
    2323</userinput></screen></para>
    2424
    25 <para>The documentation that comes with Glibc recommends to build the package
    26 not in the source directory but in a separate, dedicated directory:</para>
     25<para>The Glibc documentation recommends building Glibc outside of the source
     26directory in a dedicated build directory:</para>
    2727
    2828<para><screen><userinput>mkdir ../glibc-build
  • entities/gcc-2953.ent

    r3aa9774 r677aef3  
    1717<!ENTITY gcc-2953-patch-version "2.95.3-2">
    1818<!ENTITY gcc-2953-patch-size "4 KB">
     19<!ENTITY gcc-2953-no-fixinc-patch-version "2.95.3">
     20<!ENTITY gcc-2953-no-fixinc-patch-size "1 KB">
     21<!ENTITY gcc-2953-returntype-fix-patch-version "2.95.3">
     22<!ENTITY gcc-2953-returntype-fix-patch-size "1 KB">
    1923<!ENTITY gcc-2953-package "gcc-&gcc-2953-version;.tar.bz2">
    2024<!ENTITY gcc-2953-dir "gcc-&gcc-2953-version;">
Note: See TracChangeset for help on using the changeset viewer.