cvs commit: LFS/BOOK/entities makedev.ent

timothy at linuxfromscratch.org timothy at linuxfromscratch.org
Wed Sep 18 11:31:39 PDT 2002


timothy     02/09/18 11:31:39

  Modified:    BOOK     index.xml
               BOOK/appendixa flex-desc.xml
               BOOK/chapter01 changelog.xml how.xml
               BOOK/chapter02 aboutlfs.xml
               BOOK/chapter05 bash-inst.xml fileutils-inst.xml
               BOOK/chapter06 gcc-exp.xml ncurses-exp.xml
               BOOK/entities makedev.ent
  Log:
  Fixed typos, removed old command explanation.
  
  Revision  Changes    Path
  1.487     +2 -2      LFS/BOOK/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/index.xml,v
  retrieving revision 1.486
  retrieving revision 1.487
  diff -u -r1.486 -r1.487
  --- index.xml	14 Sep 2002 04:18:46 -0000	1.486
  +++ index.xml	18 Sep 2002 18:31:37 -0000	1.487
  @@ -4,8 +4,8 @@
   
   <!ENTITY book SYSTEM "book/book.xml">
   
  -<!ENTITY version "20020914">
  -<!ENTITY releasedate "September 14th, 2002">
  +<!ENTITY version "20020918">
  +<!ENTITY releasedate "September 18th, 2002">
   
   <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
   <!ENTITY http-root "http://ftp.linuxfromscratch.org">
  
  
  
  1.11      +2 -2      LFS/BOOK/appendixa/flex-desc.xml
  
  Index: flex-desc.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/appendixa/flex-desc.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- flex-desc.xml	4 Jun 2002 11:30:13 -0000	1.10
  +++ flex-desc.xml	18 Sep 2002 18:31:37 -0000	1.11
  @@ -12,8 +12,8 @@
   patterns in text.  Pattern recognition is very useful in many applications. 
   A user sets up rules 
   what to look for and flex will make a program that looks for those
  -patterns. The reason people use flex is that it is much easier to sets up 
  -rules for what to look for than to write the actual program that finds 
  +patterns. The reason people use flex is that it is much easier to set up 
  +rules for what to look for than to write the actual program which finds 
   the text.</para></sect4>
   
   <sect4><title>flex++</title>
  
  
  
  1.372     +4 -0      LFS/BOOK/chapter01/changelog.xml
  
  Index: changelog.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter01/changelog.xml,v
  retrieving revision 1.371
  retrieving revision 1.372
  diff -u -r1.371 -r1.372
  --- changelog.xml	13 Sep 2002 19:31:54 -0000	1.371
  +++ changelog.xml	18 Sep 2002 18:31:38 -0000	1.372
  @@ -56,6 +56,10 @@
   </itemizedlist>
   </para></listitem>
   
  +<listitem><para>September 18th, 2002 [timothy]: Chapter 06 - Ncurses:
  +Removed old <userinput>mv /lib/*.a /usr/lib</userinput> command
  +explanation.</para></listitem>
  +
   <listitem><para>September 13th, 2002 [gerard]: Chapter 06 - Shadow: Added
   --libdir=/usr/lib to the configure script options. This way a proper
   <filename>libshadow.la</filename> is generated. Also changed the
  
  
  
  1.17      +5 -3      LFS/BOOK/chapter01/how.xml
  
  Index: how.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter01/how.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- how.xml	3 Jun 2002 21:33:53 -0000	1.16
  +++ how.xml	18 Sep 2002 18:31:38 -0000	1.17
  @@ -3,7 +3,7 @@
   <?dbhtml filename="how.html" dir="chapter01"?>
   
   <para>We are going to build the LFS system by using a previously installed
  -Linux distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc.
  +Linux distribution such as Debian, SuSE, Slackware, Mandrake, RedHat, etc.
   We will use the existing Linux system as the development platform, because
   we need tools like a compiler, linker, text editor, and other necessary
   development tools to build our system. Ordinarily, the required tools are
  @@ -19,12 +19,14 @@
   build the actual system, or needed to resolve circular dependencies. For
   example, you need a compiler to build a new compiler, and you need a shell
   in order to install a new shell. The packages in this chapter will be linked
  -statically. Static linking describes a method of compiling software so that
  +statically.</para>
  +
  +<para>Static linking describes a method of compiling software so that
   it does not require the presence of libraries when building is complete.
   The resulting program is able to function on its own. The program is able to
   do so because the pieces of the program that would normally remain in the
   libraries are copied from the libraries and built right into the program.
  -Ordinarily software is built with dynamic linking. This conserves storage
  +Ordinarily, software is built with dynamic linking. This conserves storage
   space and increases the efficiency of many programs. We statically link
   our software in chapter 5 because we will in theory be moving our
   development system to a virtual environment where the already mentioned
  
  
  
  1.14      +3 -3      LFS/BOOK/chapter02/aboutlfs.xml
  
  Index: aboutlfs.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter02/aboutlfs.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- aboutlfs.xml	29 Mar 2002 12:38:41 -0000	1.13
  +++ aboutlfs.xml	18 Sep 2002 18:31:38 -0000	1.14
  @@ -10,8 +10,8 @@
   the LFS partition is mounted on /mnt/lfs.</para>
   
   <para>For example when you are told to run a command like
  -<userinput>./configure --prefix=$LFS</userinput> you actually have to
  -execute <userinput>./configure --prefix=/mnt/lfs</userinput></para>
  +<userinput>./configure --prefix=$LFS/static</userinput> you actually have to
  +execute <userinput>./configure --prefix=/mnt/lfs/static</userinput>.</para>
   
   <para>It's important that this is done no matter where it is read; be it in
   commands entered in a shell, or in a file edited or created.</para>
  @@ -23,7 +23,7 @@
   <para><screen><userinput>export LFS=/mnt/lfs</userinput></screen></para>
   
   <para>Now, if you are told to run a command like <userinput>./configure
  ---prefix=$LFS</userinput> you can type that literally. Your shell will
  +--prefix=$LFS/static</userinput> you can type that literally. Your shell will
   replace $LFS with /mnt/lfs when it processes the command line (meaning
   when you hit enter after having typed the command).</para>
   
  
  
  
  1.31      +1 -1      LFS/BOOK/chapter05/bash-inst.xml
  
  Index: bash-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/bash-inst.xml,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- bash-inst.xml	13 Sep 2002 02:23:42 -0000	1.30
  +++ bash-inst.xml	18 Sep 2002 18:31:38 -0000	1.31
  @@ -9,7 +9,7 @@
   
   <para>If both of the files are missing, you have to install the Ncurses
   development package. This package is often called something like 
  -<emphasis>Ncurses-dev</emphasis>. If this package is already installed,
  +<emphasis>ncurses-dev</emphasis>. If 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, then 
   create <filename>libcurses.a</filename> as a symlink by running the 
  
  
  
  1.43      +1 -1      LFS/BOOK/chapter05/fileutils-inst.xml
  
  Index: fileutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/fileutils-inst.xml,v
  retrieving revision 1.42
  retrieving revision 1.43
  diff -u -r1.42 -r1.43
  --- fileutils-inst.xml	29 Jul 2002 18:12:02 -0000	1.42
  +++ fileutils-inst.xml	18 Sep 2002 18:31:38 -0000	1.43
  @@ -14,7 +14,7 @@
   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 the time.</para>
  +unavailable at this time.</para>
   
   <para>To fix this package to compile properly on AMD/Glibc-2.2.3
   machines, run the following command. Do <emphasis>not</emphasis>
  
  
  
  1.12      +5 -8      LFS/BOOK/chapter06/gcc-exp.xml
  
  Index: gcc-exp.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/gcc-exp.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- gcc-exp.xml	12 Sep 2002 17:15:29 -0000	1.11
  +++ gcc-exp.xml	18 Sep 2002 18:31:39 -0000	1.12
  @@ -7,13 +7,10 @@
   
   <para><userinput>--enable-clocale=gnu:</userinput> There is a risk that
   some people will build ABI incompatible C++ libraries if they didn't install
  -all the glibc localedata. Using --enable-clocale=gnu ensures that the "right
  -thing" is done in all cases. If you don't want to use this option and don't
  -want to build all the locales, then at least make sure you installed the
  -<emphasis>de_DE</emphasis> locale with Glibc, since that's the specific locale
  -GCC will check for to determine which locale mode to use (if de_DE is
  -found, <emphasis>gnu</emphasis> mode is used, which is the corrent one to
  -use).</para>
  +all of the glibc localedata. Using --enable-clocale=gnu ensures that the
  +"right thing" is done in all cases. If you don't wish to use this option,
  +then at least build the <emphasis>de_DE</emphasis> locale. When GCC finds
  +this specific locale, then the correct locale mode (<emphasis>gnu</emphasis>)
  +is implemented.</para>
   
   </sect2>
  -
  
  
  
  1.21      +0 -5      LFS/BOOK/chapter06/ncurses-exp.xml
  
  Index: ncurses-exp.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/ncurses-exp.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- ncurses-exp.xml	12 Sep 2002 17:39:25 -0000	1.20
  +++ ncurses-exp.xml	18 Sep 2002 18:31:39 -0000	1.21
  @@ -8,11 +8,6 @@
   <para><userinput>--with-shared:</userinput> This enables the build of the
   shared ncurses library files.</para>
   
  -<para><userinput>mv /lib/*.a /usr/lib :</userinput> This
  -moves all of the static ncurses library files from /lib to /usr/lib.
  -/lib should only contain the shared files which are essential to the
  -system when /usr may not be mounted.</para>
  -
   <para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
   executable.  Ncurses install routine doesn't set the permissions
   properly so we do it manually instead.</para>
  
  
  
  1.7       +1 -1      LFS/BOOK/entities/makedev.ent
  
  Index: makedev.ent
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/entities/makedev.ent,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- makedev.ent	14 Sep 2002 02:25:10 -0000	1.6
  +++ makedev.ent	18 Sep 2002 18:31:39 -0000	1.7
  @@ -13,7 +13,7 @@
   <!ENTITY makedev-depversion "1.5">
   <!ENTITY makedev-contversion "1.5">
   <!ENTITY makedev-size "8 KB">
  -<!ENTITY makedev-package "MAKEDEV-&makedev-version;.tar.bz2">
  +<!ENTITY makedev-package "MAKEDEV-&makedev-version;.bz2">
   
   <!ENTITY makedev-compsize "50 KB">
   <!ENTITY makedev-time "0.07 SBU">
  
  
  
-- 
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