cvs commit: LFS/BOOK/chapter05 bash-inst.xml binutils-inst.xml diffutils-inst.xml fileutils-inst.xml gcc-inst.xml shellutils-inst.xml

gerard at linuxfromscratch.org gerard at linuxfromscratch.org
Mon Jan 27 13:28:02 PST 2003


gerard      03/01/27 16:28:02

  Modified:    BOOK     index.xml
               BOOK/chapter05 bash-inst.xml binutils-inst.xml
                        diffutils-inst.xml fileutils-inst.xml gcc-inst.xml
                        shellutils-inst.xml
  Log:
  minor textual changes to chapter 5
  
  Revision  Changes    Path
  1.545     +1 -1      LFS/BOOK/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/index.xml,v
  retrieving revision 1.544
  retrieving revision 1.545
  diff -u -r1.544 -r1.545
  --- index.xml	22 Jan 2003 20:08:30 -0000	1.544
  +++ index.xml	27 Jan 2003 21:28:02 -0000	1.545
  @@ -5,7 +5,7 @@
   <!ENTITY book SYSTEM "book/book.xml">
   
   <!ENTITY version "20030122">
  -<!ENTITY releasedate "January 22nd, 2003">
  +<!ENTITY releasedate "January 27nd, 2003">
   
   <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
   <!ENTITY http-root "http://ftp.linuxfromscratch.org">
  
  
  
  1.41      +2 -2      LFS/BOOK/chapter05/bash-inst.xml
  
  Index: bash-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/bash-inst.xml,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -r1.40 -r1.41
  --- bash-inst.xml	18 Jan 2003 23:23:45 -0000	1.40
  +++ bash-inst.xml	27 Jan 2003 21:28:02 -0000	1.41
  @@ -15,7 +15,7 @@
   this package is already installed, or you just installed it, check for the
   two files again. Often the <filename>libcurses.a</filename> file is (still)
   missing. If so, create <filename>libcurses.a</filename> as a symlink
  -by running the following commands as user <emphasis>root:</emphasis></para>
  +by running the following command as user <emphasis>root:</emphasis></para>
   
   <para><screen><userinput>ln -s libncurses.a /usr/lib/libcurses.a</userinput></screen></para>
   
  @@ -50,7 +50,7 @@
   where we will use libncurses), but it's a good test to make sure that
   the Ncurses package has been installed properly. If not, you will get in
   trouble later on in this chapter when you install the Texinfo package.
  -That package requires ncurses, and termcap can't reliably be used
  +That package requires ncurses, and termcap can't be used
   there.</para></listitem>
   </itemizedlist>
   
  
  
  
  1.20      +1 -2      LFS/BOOK/chapter05/binutils-inst.xml
  
  Index: binutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/binutils-inst.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- binutils-inst.xml	11 Jan 2003 17:41:17 -0000	1.19
  +++ binutils-inst.xml	27 Jan 2003 21:28:02 -0000	1.20
  @@ -7,8 +7,7 @@
   optimization flags (including the -march and -mcpu options). Binutils is
   best left alone. Therefore, if you have defined any environment variables
   that override default optimizations, such as CFLAGS and CXXFLAGS, we
  -recommend unsetting or modifying them when building binutils. You have been
  -warned.</para>
  +recommend unsetting or modifying them when building binutils.</para>
   
   <para>It is recommended by the Binutils installation documentation to build
   Binutils outside of the source directory in a dedicated directory:</para>
  
  
  
  1.20      +4 -3      LFS/BOOK/chapter05/diffutils-inst.xml
  
  Index: diffutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/diffutils-inst.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- diffutils-inst.xml	16 Jan 2003 01:08:41 -0000	1.19
  +++ diffutils-inst.xml	27 Jan 2003 21:28:02 -0000	1.20
  @@ -13,11 +13,12 @@
   <itemizedlist>
   <listitem><para><userinput>LDFLAGS="-static":</userinput> This is the most
   common way to tell a package that all programs should be statically linked.
  -This way the <emphasis>LDFLAGS</emphasis> environment variable is set but
  +This way the <emphasis>LDFLAGS</emphasis> environment variable is set, but
   only in the subshell that the <filename>configure</filename> script runs
   in. When <userinput>configure</userinput> has done its job, the
  -<emphasis>LDFLAGS</emphasis> variable won't exist
  -anymore.</para></listitem>
  +<emphasis>LDFLAGS</emphasis> environment variable won't exist anymore
  +and the <filename>Makefile</filename> files contain will contain this
  +variable locally.</para></listitem>
   
   <listitem><para><userinput>CPPFLAGS=-Dre_max_failures=re_max_failures2:</userinput>
   The <emphasis>CPPFLAGS</emphasis> variable is a variable that's read by the
  
  
  
  1.49      +3 -3      LFS/BOOK/chapter05/fileutils-inst.xml
  
  Index: fileutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/fileutils-inst.xml,v
  retrieving revision 1.48
  retrieving revision 1.49
  diff -u -r1.48 -r1.49
  --- fileutils-inst.xml	13 Jan 2003 13:26:44 -0000	1.48
  +++ fileutils-inst.xml	27 Jan 2003 21:28:02 -0000	1.49
  @@ -15,13 +15,13 @@
   and has Glibc-2.2.3 (or higher) installed. If that's the case, you'll need
   to remove the fileutils-&fileutils-version; directory and unpack it again
   from the tarball before continuing. We believe this may be the case when
  -your distribution has altered Glibc-2.2.3 somehow, but details are
  -unavailable at this time.</para>
  +your distribution has altered Glibc-2.2.3 somehow, but the exact details
  +are unknown.</para>
   
   <para>To fix this package to compile properly on AMD/Glibc-2.2.3
   machines, run the following command. Do <emphasis>NOT</emphasis>
   attempt this fix if you don't have Glibc-2.2.3 installed. It will more 
  -than likely result in all kinds of compile time problems.</para>
  +than likely result in all kinds of compilation problems.</para>
   
   <para><screen><userinput>patch -Np1 -i ../fileutils-&fileutils-patch-version;.patch</userinput></screen></para>
   
  
  
  
  1.49      +4 -4      LFS/BOOK/chapter05/gcc-inst.xml
  
  Index: gcc-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/gcc-inst.xml,v
  retrieving revision 1.48
  retrieving revision 1.49
  diff -u -r1.48 -r1.49
  --- gcc-inst.xml	11 Jan 2003 18:04:51 -0000	1.48
  +++ gcc-inst.xml	27 Jan 2003 21:28:02 -0000	1.49
  @@ -10,8 +10,7 @@
   default optimization flags (including the -march and -mcpu options). GCC is
   best left alone. Therefore, if you have defined any environment variables
   that override default optimizations, such as CFLAGS and CXXFLAGS, we
  -recommend unsetting or modifying them when building GCC. You have
  -been warned.</para>
  +recommend unsetting or modifying them when building GCC.</para>
   
   <para>It is recommended by the GCC installation documentation to build
   GCC outside of the source directory in a dedicated directory:</para>
  @@ -32,7 +31,8 @@
   <listitem><para><userinput>--prefix=/static:</userinput> This is NOT a
   typo. GCC hard codes some paths while compiling and so we need to pass
   <filename class="directory">/static</filename> as the prefix during the
  -configure stage. We pass the real install prefix during the installation
  +configure stage. We will pass the real installation prefix (<filename
  +class="directory">$LFS/static</filename> during the installation
   stage later on.</para></listitem>
   
   <listitem><para><userinput>--disable-shared:</userinput> This prevents the
  @@ -82,7 +82,7 @@
   <filename>$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2</filename>. Later on
   in chapter 6 you will install Glibc which will put its header files in
   <filename>/usr/include</filename>. Next you will install other programs that
  -use the Glibc headers. GCC will look in
  +use the Glibc headers and GCC will look in
   <filename>/static/lib/gcc-lib</filename> before looking in
   <filename>/usr/include</filename>, with the result of finding and using the
   fixed Glibc header files from your host distribution, which are probably
  
  
  
  1.32      +1 -2      LFS/BOOK/chapter05/shellutils-inst.xml
  
  Index: shellutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/shellutils-inst.xml,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- shellutils-inst.xml	15 Jan 2003 02:58:53 -0000	1.31
  +++ shellutils-inst.xml	27 Jan 2003 21:28:02 -0000	1.32
  @@ -31,8 +31,7 @@
   <para>You can safely ignore that warning. You need to be logged in as root
   in order to install su the way Sh-utils wants to install it, which is being
   suid root. Because we don't need su during Chapter 6, and su will be properly
  -installed when we re-install Sh-utils in Chapter 6, you can just
  -pretend you didn't see it.</para>
  +installed when we re-install Sh-utils in Chapter 6.</para>
   
   </sect2>
   
  
  
  
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-book' in the subject header of the message



More information about the lfs-book mailing list