Upgraded to Glibc-2.3.3, Kbd-1.12, Perl-5.8.3 and Shadow-4.0.4.1.

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

5 files changed, 31 insertions, 43 deletions

diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml
index 11e7226c5..02f771868 100644
--- a/chapter06/binutils.xml
+++ b/chapter06/binutils.xml
@@ -28,8 +28,8 @@ everything is set up correctly by performing a simple test:</para>
 <para>Your chroot environment is not set up for proper PTY operation. In this
 case there is no point in running the test suites for Binutils and GCC until you
 are able to resolve the issue. Please refer back to <xref linkend="ch06-proc"/>
-and <xref linkend="ch06-MAKEDEV"/> and perform the recommended steps to fix the
-problem.</para>
+and the <xref linkend="ch06-MAKEDEV"/> section and perform the recommended steps
+to fix the problem.</para>
 
 <note><para>The test suite for Binutils in this section is considered
 <emphasis>critical</emphasis>. Our advice is to not skip it under any
diff --git a/chapter06/coreutils.xml b/chapter06/coreutils.xml
index 9ceb62437..815a272c5 100644
--- a/chapter06/coreutils.xml
+++ b/chapter06/coreutils.xml
@@ -16,6 +16,10 @@ Estimated required disk space:  &coreutils-compsize;</screen>
 <sect2>
 <title>Installation of Coreutils</title>
 
+<para>Apply the same "Posixver" patch we used previously:</para>
+
+<screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
+
 <para>Normally the functionality of <userinput>uname</userinput> is somewhat
 broken, in that the <userinput>-p</userinput> switch always returns "unknown".
 The following patch fixes this behaviour for Intel architectures:</para>
diff --git a/chapter06/glibc.xml b/chapter06/glibc.xml
index 5bb78e198..3009a84d2 100644
--- a/chapter06/glibc.xml
+++ b/chapter06/glibc.xml
@@ -28,14 +28,8 @@ results and thus defeat our goal of achieving a clean build.</para>
 <emphasis>critical</emphasis>. Our advice is to not skip it under any
 circumstance.</para></note>
 
-<para>Before starting to build Glibc, remember to unpack the Glibc-linuxthreads
-again inside the <filename>glibc-&glibc-version;</filename> directory, and to
-unset any environment variables that override the default optimization
-flags.</para>
-
-<para>Apply the same patch we used previously:</para>
-                                                                                
-<screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen>
+<para>Before starting to build Glibc, remember to unset any environment
+variables that override the default optimization flags.</para>
 
 <para>The Glibc documentation recommends building Glibc outside of the source
 directory in a dedicated build directory:</para>
@@ -45,9 +39,10 @@ cd ../glibc-build</userinput></screen>
 
 <para>Now prepare Glibc for compilation:</para>
 
-<screen><userinput>../glibc-&glibc-version;/configure --prefix=/usr \
-&nbsp;&nbsp;&nbsp;&nbsp;--disable-profile --enable-add-ons \
-&nbsp;&nbsp;&nbsp;&nbsp;--libexecdir=/usr/lib --with-headers=/usr/include</userinput></screen>
+<screen><userinput>../&glibc-dir;/configure --prefix=/usr \
+&nbsp;&nbsp;&nbsp;&nbsp;--disable-profile --enable-add-ons=linuxthreads \
+&nbsp;&nbsp;&nbsp;&nbsp;--libexecdir=/usr/lib --with-headers=/usr/include \
+&nbsp;&nbsp;&nbsp;&nbsp;--without-cvs</userinput></screen>
 
 <para>The meaning of the new configure options:</para>
 
@@ -95,14 +90,14 @@ weren't installed by the above command. Do it with this:</para>
 <screen><userinput>make localedata/install-locales</userinput></screen>
 
 <para>An alternative to running the previous command is to install only those
-locales which you need or want. This can be achieved using the
+locales which you need or want. This can be achieved by using the
 <userinput>localedef</userinput> command. Information on this can be found in
-the <filename>INSTALL</filename> file in the
-<filename>glibc-&glibc-version;</filename> tree. However,  there are a number
-of locales that are essential for the tests of future packages to pass
-correctly. The following instructions, in place of the install-locales
-command above, will install the minimum set of locales necessary for the
-tests to run successfully:</para>
+the <filename>INSTALL</filename> file in the Glibc source. However, there are
+a number of locales that are essential for the tests of future packages to
+pass, in particular, the <emphasis>libstdc++</emphasis> tests from GCC. The
+following instructions, instead of the install-locales target above, will
+install the minimum set of locales necessary for the tests to run
+successfully:</para>
 
 <screen><userinput>mkdir -p /usr/lib/locale
 localedef -i de_DE -f ISO-8859-1 de_DE
diff --git a/chapter06/shadowpwd.xml b/chapter06/shadowpwd.xml
index 89cfd5d39..a89df4002 100644
--- a/chapter06/shadowpwd.xml
+++ b/chapter06/shadowpwd.xml
@@ -27,15 +27,14 @@ the package incorrectly assumes it is going to be located at
 
 <screen><userinput>touch /usr/bin/passwd</userinput></screen>
 
-<para>The current Shadow suite has a problem that causes the
-<userinput>newgrp</userinput> command to fail.  The following patch (also
-appearing in Shadow's CVS code) fixes this problem:</para>
+<para>Now prepare Shadow for compilation:</para>
 
-<screen><userinput>patch -Np1 -i ../&shadow-patch;</userinput></screen>
+<screen><userinput>./configure --libdir=/usr/lib --enable-shared</userinput></screen>
 
-<para>Now prepare Shadow for compilation:</para>
+<para>Work around a problem that prevents Shadow's internationalization from
+working:</para>
 
-<screen><userinput>./configure --prefix=/usr --libdir=/usr/lib --enable-shared</userinput></screen>
+<screen><userinput>echo '#define HAVE_SETLOCALE 1' >> config.h</userinput></screen>
 
 <para>Compile the package:</para>
 
@@ -65,20 +64,10 @@ relevant configuration file while copying it to its destination:</para>
 <note><para>Be extra careful when typing all of the above. It is probably safer
 to cut-and-paste it rather than try and type it all in.</para></note>
 
-<para>According to the man page of <userinput>vipw</userinput>, a
-<userinput>vigr</userinput> program should exist too. Since the installation
-procedure doesn't create this program, create a symlink manually:</para>
-
-<screen><userinput>ln -s vipw /usr/sbin/vigr</userinput></screen>
-
-<para>As the <filename>/bin/vipw</filename> symlink is redundant (and even
-pointing to a non-existent file), remove it:</para>
-
-<screen><userinput>rm /bin/vipw</userinput></screen>
-
-<para>Now move the <userinput>sg</userinput> program to its proper place:</para>
+<para>Move some misplaced symlinks to their proper locations:</para>
 
-<screen><userinput>mv /bin/sg /usr/bin</userinput></screen>
+<screen><userinput>mv /bin/sg /usr/bin
+mv /bin/vigr /usr/sbin</userinput></screen>
 
 <para>And move Shadow's dynamic libraries to a more appropriate location:</para>
 
@@ -95,9 +84,9 @@ directory for it to work properly:</para>
 
 <screen><userinput>mkdir /etc/default</userinput></screen>
 
-<para>Coreutils has already installed a <userinput>groups</userinput> program
-in <filename>/usr/bin</filename>. If you wish, you can remove the one
-installed by Shadow:</para>
+<para>Coreutils has already installed a better <userinput>groups</userinput>
+program in <filename>/usr/bin</filename>. Remove the one installed by
+Shadow:</para>
 
 <screen><userinput>rm /bin/groups</userinput></screen>
 
diff --git a/chapter06/vim.xml b/chapter06/vim.xml
index 06a10aebc..e4ab8dba2 100644
--- a/chapter06/vim.xml
+++ b/chapter06/vim.xml
@@ -42,7 +42,7 @@ echo '#define SYS_GVIMRC_FILE "/etc/gvimrc"' &gt;&gt; src/feature.h</userinput><
 <para>This package has a test suite available which performs a number of
 checks to ensure it will function correctly. However, the Vim test suite will
 output a whole lot of seemingly garbage characters to screen which can
-sometimes wreak havoc with the running terminal. Accordingly, the running of
+occasionally wreak havoc with the running terminal. Accordingly, the running of
 the test suite here is optional. Should you choose to run the Vim test suite,
 the following command will do so:</para>