Ignore:
Timestamp:
01/03/2003 02:57:38 AM (21 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_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:
8836e60
Parents:
4d51529
Message:

fix typos - alex' patch

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/gcc-exp.xml

    r4d51529 r72bab45  
    1919
    2020<para><userinput>make install-no-fixedincludes:</userinput>
    21 This prevents the fixed header files from being installed. This is needed
    22 because under normal circumstances the GCC installation will run the
    23 fixincludes scripts which scans your system for header files that need to be
    24 fixed. Say it finds Glibc header files. It will fix them and will end up in
    25 $LFS/static/lib/gcc-lib/i686-pc-linux-gnu/ Later on in chapter 6 you
    26 will install Glibc which will install header files in /usr/include. Next
    27 you will install other programs which will use Glibc headers. GCC will look
    28 in /static/lib/gcc-lib before looking in /usr/include, which has the result
    29 of Glibc header files from your host distribution being found and used which
    30 are probably incompatible with the Glibc version actually in use on the LFS
    31 system.</para>
     21This prevents the fixincludes script from running. Preventing this is
     22necessary because under normal circumstances the GCC installation will run
     23the fixincludes script which scans your system for header files that need to
     24be fixed. It might find that the Glibc header files of your host system need
     25to be fixed. If so, it will fix them and put them in
     26<filename>$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2</filename>.
     27Later on in chapter 6 you will install Glibc which will put its header
     28files in <filename>/usr/include</filename>. Next you will install other
     29programs that use the Glibc headers. GCC will look in
     30<filename>/static/lib/gcc-lib</filename> before looking in
     31<filename>/usr/include</filename>, with the result of finding and using
     32the fixed Glibc header files from your host distribution, which are probably
     33incompatible with the Glibc version actually used on the LFS system.</para>
    3234
    3335<para><userinput>ln -s gcc $LFS/static/bin/cc:</userinput> This
Note: See TracChangeset for help on using the changeset viewer.