gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-01-31 19:32:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Bill's typo fixes

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2427 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2003-02-05 18:29:23 +00:00
parent 68ed9a53ee
commit fdfb226af0
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
chapter05/findutils-inst.xml
View File

@ -5,7 +5,7 @@
<para>The Findutils package is quite old and it has problems compiling
against newer Glibc versions (Glibc-2.0.x and up). You need to apply the
patch which fixes the following issues:</para>
patch, which fixes the following issues:</para>
<itemizedlist>
<listitem><para>Findutils declares a function called basename, but this
@ -13,14 +13,14 @@ function name is already used by the C standard libraries. This patch
changes the Findutils version of basename function so that it is called
basename2 instead.</para></listitem>
<listitem><para>Findutils uses an incorrect way to use library files. It
<listitem><para>Findutils uses library files in an incorrect way. It
declares library functions, to tell the compiler what the name of the
function will be when the libraries are linked in. This syntax is invalid
and causes compiler warnings/errors. This patch removes this improper
syntax.</para></listitem>
<listitem><para>Every GNU package is supposed use a macro called _GNU_SOURCE.
This macro enables declarations of GNU library extension functions and so the
This macro enables declarations of GNU library extension functions so the
compiler will be able to detect name conflicts between functions more easily.
This patch adds this macro to the source code.</para></listitem>
</itemizedlist>

4
chapter06/findutils-inst.xml
View File

@ -5,7 +5,7 @@
<para>The Findutils package is quite old and it has problems compiling
against newer Glibc versions (Glibc-2.0.x and up). You need to apply the
patch which fixes the following issues:</para>
patch, which fixes the following issues:</para>
<itemizedlist>
<listitem><para>Findutils declares a function called basename, but this
@ -13,7 +13,7 @@ function name is already used by the C standard libraries. This patch
changes the Findutils version of basename function so that it is called
basename2 instead.</para></listitem>
<listitem><para>Findutils uses an incorrect way to use library files. It
<listitem><para>Findutils uses library files in an incorrect way. It
declares library functions, to tell the compiler what the name of the
function will be when the libraries are linked in. This syntax is invalid
and causes compiler warnings/errors. This patch removes this improper

6
chapter06/gawk-inst.xml
View File

@ -3,13 +3,13 @@
<sect2>
<title>Installation of Gawk</title>
<para>Before installing the Gawk package you have to apply a patch to it
<para>Before installing the Gawk package you have to apply a patch,
which fixes the following issues:</para>
<itemizedlist>
<listitem><para>Gawk's default location for libexecdir is <filename
class="directory">$prefix/libexecdir/awk</filename>. This location doesn't
comply with FHS (FHS never mentions a directory called
comply with FHS (which never mentions a directory called
libexecdir).</para></listitem>
<listitem><para>The patch allows us to pass
@ -20,7 +20,7 @@ the book).</para></listitem>
<listitem><para>The default data directory for gawk is <filename
class="directory">$prefix/share/awk</filename>. A package specific
directory should be named after the package and the version (gawk-3.1.1
directory should be named using the package and version (like gawk-3.1.1
instead of awk) because there may be more than one awk interpreter on a
system (and more than one version of gawk). The patch changes this to
<filename class="directory">$prefix/share/gawk-3.1.1</filename> to be more

2
chapter06/gzip-inst.xml
View File

@ -6,7 +6,7 @@
<para>The following patch fixes a buffer overflow that occurs when a
filename is longer than 1020 characters. It does this by inserting a check
that the buffer is large enough for the given filename. The program exits
with the message "Filename too long" the buffer is not large enough.</para>
with the message "Filename too long" if the buffer is not large enough.</para>
<para><screen><userinput>patch -Np1 -i ../gzip-&gzip-patch-version;.patch</userinput></screen></para>