Changeset 878b2a4b


Ignore:
Timestamp:
02/02/2004 10:15:46 PM (20 years ago)
Author:
Alex Gronenwoud <alex@…>
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, 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:
0aa644e2
Parents:
add6877
Message:

Rewording a few introductory paragraphs.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/chapter05.xml

    radd6877 r878b2a4b  
    2323them to pollute the soon-to-be LFS system.</para>
    2424
    25 <para>The build instructions assume that you are using the
    26 <command>bash</command> shell. It is also expected that you have already
    27 unpacked a source package (while logged in as user <emphasis>lfs</emphasis> --
    28 explained shortly) and performed a <userinput>cd</userinput> into the source
    29 directory of a package before issuing its build commands.</para>
     25<para>Before issuing the build instructions for a package you are expected to
     26have already unpacked it as user <emphasis>lfs</emphasis> (explained shortly),
     27and to have performed a <userinput>cd</userinput> into the created directory.
     28The build instructions assume that you are using the <command>bash</command>
     29shell.</para>
    3030
    3131<para>Several of the packages are patched before compilation, but only when
    3232the patch is needed to circumvent a problem. Often the patch is needed in
    3333both this and the next chapter, but sometimes in only one of them. Therefore,
    34 don't worry when instructions for a downloaded patch seem to be missing. When
    35 applying a patch you'll occasionally see a warning message about
     34don't worry when instructions for a downloaded patch seem to be missing. Also,
     35when applying a patch, you'll occasionally see warning messages about
    3636<emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>. These warnings are
    37 nothing to worry about as the patch was still successfully applied.</para>
    38 
    39 <para>During the installation of most packages you will
    40 see all kinds of compiler warnings scroll by on your screen. These are
    41 normal and can be safely ignored. They are just what they say they are:
    42 warnings -- mostly about deprecated, but not invalid, use of the C or C++
    43 syntax. It's just that C standards have changed rather often and some
    44 packages still use the older standard, which is not really a problem.</para>
    45 
    46 <para><emphasis>Unless</emphasis> told not to, you should normally delete the
    47 source and build directories after installing each package -- for cleanness
    48 sake and to save space.</para>
    49 
    50 <para>Before continuing, make sure the LFS environment variable is set up
    51 properly by executing the following:</para>
     37nothing to worry about, as the patch was still successfully applied.</para>
     38
     39<para>During the compilation of most packages you will see many warnings
     40scroll by on your screen. These are normal and can safely be ignored. They are
     41just what they say they are: warnings -- mostly about deprecated, but not
     42invalid, use of the C or C++ syntax. It's just that C standards have changed
     43rather often and some packages still use the older standard, which is not
     44really a problem.</para>
     45
     46<para>After installing each package you should delete its source and build
     47directories, <emphasis>unless</emphasis> told otherwise. Deleting the sources
     48saves space, but also prevents misconfiguration when the same package is
     49reinstalled further on. Only for three packages you will need to keep the
     50source and build directories around for a while, so their contents can be used
     51by later commands. Do not miss the reminders.</para>
     52
     53<para>Now first check that your LFS environment variable is set up
     54properly:</para>
    5255
    5356<screen><userinput>echo $LFS</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.