From 878b2a4beedc4c4770a33a84c9a7260ebcefd901 Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Mon, 2 Feb 2004 22:15:46 +0000 Subject: Rewording a few introductory paragraphs. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3210 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/chapter05.xml | 47 +++++++++++++++++++++++++---------------------- 1 file changed, 25 insertions(+), 22 deletions(-) diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index 0349addd0..c4e45d336 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -22,33 +22,36 @@ to keep them separate from the files installed in the next chapter. Since the packages compiled here are merely temporary, we don't want them to pollute the soon-to-be LFS system. -The build instructions assume that you are using the -bash shell. It is also expected that you have already -unpacked a source package (while logged in as user lfs -- -explained shortly) and performed a cd into the source -directory of a package before issuing its build commands. +Before issuing the build instructions for a package you are expected to +have already unpacked it as user lfs (explained shortly), +and to have performed a cd into the created directory. +The build instructions assume that you are using the bash +shell. Several of the packages are patched before compilation, but only when the patch is needed to circumvent a problem. Often the patch is needed in both this and the next chapter, but sometimes in only one of them. Therefore, -don't worry when instructions for a downloaded patch seem to be missing. When -applying a patch you'll occasionally see a warning message about +don't worry when instructions for a downloaded patch seem to be missing. Also, +when applying a patch, you'll occasionally see warning messages about offset or fuzz. These warnings are -nothing to worry about as the patch was still successfully applied. - -During the installation of most packages you will -see all kinds of compiler warnings scroll by on your screen. These are -normal and can be safely ignored. They are just what they say they are: -warnings -- mostly about deprecated, but not invalid, use of the C or C++ -syntax. It's just that C standards have changed rather often and some -packages still use the older standard, which is not really a problem. - -Unless told not to, you should normally delete the -source and build directories after installing each package -- for cleanness -sake and to save space. - -Before continuing, make sure the LFS environment variable is set up -properly by executing the following: +nothing to worry about, as the patch was still successfully applied. + +During the compilation of most packages you will see many warnings +scroll by on your screen. These are normal and can safely be ignored. They are +just what they say they are: warnings -- mostly about deprecated, but not +invalid, use of the C or C++ syntax. It's just that C standards have changed +rather often and some packages still use the older standard, which is not +really a problem. + +After installing each package you should delete its source and build +directories, unless told otherwise. Deleting the sources +saves space, but also prevents misconfiguration when the same package is +reinstalled further on. Only for three packages you will need to keep the +source and build directories around for a while, so their contents can be used +by later commands. Do not miss the reminders. + +Now first check that your LFS environment variable is set up +properly: echo $LFS -- cgit v1.2.3-54-g00ecf