Changeset fdfb226


Ignore:
Timestamp:
02/05/2003 06:29:23 PM (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:
d67368f
Parents:
68ed9a53
Message:

Bill's typo fixes

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

Files:
4 edited

Legend:

Unmodified
Added
Removed
  • chapter05/findutils-inst.xml

    r68ed9a53 rfdfb226  
    66<para>The Findutils package is quite old and it has problems compiling
    77against newer Glibc versions (Glibc-2.0.x and up). You need to apply the
    8 patch which fixes the following issues:</para>
     8patch, which fixes the following issues:</para>
    99
    1010<itemizedlist>
     
    1414basename2 instead.</para></listitem>
    1515
    16 <listitem><para>Findutils uses an incorrect way to use library files. It
     16<listitem><para>Findutils uses library files in an incorrect way. It
    1717declares library functions, to tell the compiler what the name of the
    1818function will be when the libraries are linked in. This syntax is invalid
     
    2121
    2222<listitem><para>Every GNU package is supposed use a macro called _GNU_SOURCE.
    23 This macro enables declarations of GNU library extension functions and so the
     23This macro enables declarations of GNU library extension functions so the
    2424compiler will be able to detect name conflicts between functions more easily.
    2525This patch adds this macro to the source code.</para></listitem>
  • chapter06/findutils-inst.xml

    r68ed9a53 rfdfb226  
    66<para>The Findutils package is quite old and it has problems compiling
    77against newer Glibc versions (Glibc-2.0.x and up). You need to apply the
    8 patch which fixes the following issues:</para>
     8patch, which fixes the following issues:</para>
    99
    1010<itemizedlist>
     
    1414basename2 instead.</para></listitem>
    1515
    16 <listitem><para>Findutils uses an incorrect way to use library files. It
     16<listitem><para>Findutils uses library files in an incorrect way. It
    1717declares library functions, to tell the compiler what the name of the
    1818function will be when the libraries are linked in. This syntax is invalid
  • chapter06/gawk-inst.xml

    r68ed9a53 rfdfb226  
    44<title>Installation of Gawk</title>
    55
    6 <para>Before installing the Gawk package you have to apply a patch to it
     6<para>Before installing the Gawk package you have to apply a patch,
    77which fixes the following issues:</para>
    88
     
    1010<listitem><para>Gawk's default location for libexecdir is <filename
    1111class="directory">$prefix/libexecdir/awk</filename>. This location doesn't
    12 comply with FHS (FHS never mentions a directory called
     12comply with FHS (which never mentions a directory called
    1313libexecdir).</para></listitem>
    1414
     
    2121<listitem><para>The default data directory for gawk is <filename
    2222class="directory">$prefix/share/awk</filename>. A package specific
    23 directory should be named after the package and the version (gawk-3.1.1
     23directory should be named using the package and version (like gawk-3.1.1
    2424instead of awk) because there may be more than one awk interpreter on a
    2525system (and more than one version of gawk). The patch changes this to
  • chapter06/gzip-inst.xml

    r68ed9a53 rfdfb226  
    77filename is longer than 1020 characters. It does this by inserting a check
    88that the buffer is large enough for the given filename. The program exits
    9 with the message "Filename too long" the buffer is not large enough.</para>
     9with the message "Filename too long" if the buffer is not large enough.</para>
    1010
    1111<para><screen><userinput>patch -Np1 -i ../gzip-&gzip-patch-version;.patch</userinput></screen></para>
Note: See TracChangeset for help on using the changeset viewer.