Changeset 677aef3
- Timestamp:
- 09/22/2003 02:25:37 PM (21 years ago)
- 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
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/chapter04.xml
r3aa9774 r677aef3 252 252 <ulink url="&http;/gawk-&gawk-patch-version;.patch"/> 253 253 254 GCC Patch (&gcc-2953-patch-version;) - &gcc-2953-patch-size;:254 GCC-2 Patch (&gcc-2953-patch-version;) - &gcc-2953-patch-size;: 255 255 <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"/> 256 GCC-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"/> 258 GCC-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"/> 259 260 260 261 GCC No Fixincludes Patch: -
chapter05/binutils-pass1-inst.xml
r3aa9774 r677aef3 19 19 modifying them when building Binutils.</para> 20 20 21 <para> It is recommended by the Binutils installation documentation to build22 Binutils outside of the source directory in a dedicated directory:</para>21 <para>The Binutils documentation recommends building Binutils outside of the 22 source directory in a dedicated build directory:</para> 23 23 24 24 <para><screen><userinput>mkdir ../binutils-build -
chapter05/binutils-pass2-inst.xml
r3aa9774 r677aef3 8 8 </note> 9 9 10 <para> First create a separate build directory again:</para>10 <para>Create a separate build directory again:</para> 11 11 12 12 <para><screen><userinput>mkdir ../binutils-build -
chapter05/gcc-pass1-inst.xml
r3aa9774 r677aef3 18 18 or modifying them when building GCC.</para> 19 19 20 <para> It is recommended by the GCC installation documentation to build21 GCC outside of the source directory in a dedicated directory:</para>20 <para>The GCC documentation recommends building GCC outside of the source 21 directory in a dedicated build directory:</para> 22 22 23 23 <para><screen><userinput>mkdir ../gcc-build -
chapter05/glibc-inst.xml
r3aa9774 r677aef3 35 35 </userinput></screen></para> 36 36 37 <para>The documentation that comes with Glibc recommends to build the package38 not in the source directory but in a separate, dedicated directory:</para>37 <para>The Glibc documentation recommends building Glibc outside of the source 38 directory in a dedicated build directory:</para> 39 39 40 40 <para><screen><userinput>mkdir ../glibc-build -
chapter06/binutils-inst.xml
r3aa9774 r677aef3 13 13 or modifying them when building Binutils.</para> 14 14 15 <para> It is recommended by the Binutils installation documentation to build16 Binutils outside of the sourcedirectory:</para>15 <para>The Binutils documentation recommends building Binutils outside of the 16 source directory in a dedicated build directory:</para> 17 17 18 18 <para><screen><userinput>mkdir ../binutils-build -
chapter06/gcc-2953-inst.xml
r3aa9774 r677aef3 17 17 developer's advice and using the version here to compile your kernel.</para> 18 18 19 <note><para>We don't install the C++ compiler or libraries here. However, there 20 may be reasons why you would want to install them. More information can be found 21 at <ulink url="&blfs-root;view/cvs/general/gcc2.html"/>.</para></note> 22 19 23 <para>We'll install this older release of GCC into the non-standard prefix of 20 24 <filename class="directory">/opt</filename> so as to avoid interfering with … … 22 26 .</para> 23 27 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 31 patch -Np1 -i ../gcc-&gcc-2953-no-fixinc-patch-version;-no-fixinc.patch 32 patch -Np1 -i ../gcc-&gcc-2953-returntype-fix-patch-version;-returntype-fix.patch 33 echo timestamp > gcc/cstamp-h.in</userinput></screen></para> 34 35 <para>The GCC documentation recommends building GCC outside of the source 36 directory in a dedicated build directory:</para> 37 38 <para><screen><userinput>mkdir ../gcc-2-build 39 cd ../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 \ 30 44 --enable-shared --enable-languages=c \ 31 45 --enable-threads=posix -
chapter06/gcc-inst.xml
r3aa9774 r677aef3 26 26 as we will use the one provided by binutils instead.</para> 27 27 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 29 directory in a dedicated build directory:</para> 31 30 32 31 <para><screen><userinput>mkdir ../gcc-build -
chapter06/glibc-inst.xml
r3aa9774 r677aef3 23 23 </userinput></screen></para> 24 24 25 <para>The documentation that comes with Glibc recommends to build the package26 not in the source directory but in a separate, dedicated directory:</para>25 <para>The Glibc documentation recommends building Glibc outside of the source 26 directory in a dedicated build directory:</para> 27 27 28 28 <para><screen><userinput>mkdir ../glibc-build -
entities/gcc-2953.ent
r3aa9774 r677aef3 17 17 <!ENTITY gcc-2953-patch-version "2.95.3-2"> 18 18 <!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"> 19 23 <!ENTITY gcc-2953-package "gcc-&gcc-2953-version;.tar.bz2"> 20 24 <!ENTITY gcc-2953-dir "gcc-&gcc-2953-version;">
Note:
See TracChangeset
for help on using the changeset viewer.