From 3c63868dde31929aadfb518d212ff81893714e5c Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sun, 26 Oct 2008 17:47:52 +0000 Subject: Added a General Compilation Instructions section immediatley before binutils. Essentially reordered the presentation that was in the Chapter 5 Introduction. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8704 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter01/changelog.xml | 5 +++ chapter05/chapter05.xml | 1 + chapter05/generalinstructions.xml | 71 +++++++++++++++++++++++++++++++++++++++ chapter05/introduction.xml | 40 +--------------------- 4 files changed, 78 insertions(+), 39 deletions(-) create mode 100644 chapter05/generalinstructions.xml diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index f95f6cf2f..fb27ac005 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -39,6 +39,11 @@ 2008-10-26 + + [bdubbs] - Added a General Compilation Instructions section + immediatley before binutils. Essentially reordered the presentation + that was in the Chapter 5 Introduction. + [bdubbs] - Remove unnecessary mandir patch. Updated vim package contents. diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index 5fa82f6da..5d776d032 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -13,6 +13,7 @@ + diff --git a/chapter05/generalinstructions.xml b/chapter05/generalinstructions.xml new file mode 100644 index 000000000..bab8bed22 --- /dev/null +++ b/chapter05/generalinstructions.xml @@ -0,0 +1,71 @@ + + + %general-entities; +]> + + + + + General Compilation Instructions + + When building packages there are several assumptions made within + the instructions: + + + + + Several of the packages are patched before compilation, but only when + the patch is needed to circumvent a problem. A patch is often needed in + both this and the next chapter, but sometimes in only one or the other. + Therefore, do not be concerned if instructions for a downloaded patch seem + to be missing. Warning messages about offset or + fuzz may also be encountered when applying a patch. Do + not worry about these warnings, as the patch was still successfully + applied. + + + + During the compilation of most packages, there will be several + warnings that scroll by on the screen. These are normal and can safely be + ignored. These warnings are as they appear—warnings about + deprecated, but not invalid, use of the C or C++ syntax. C standards change + fairly often, and some packages still use the older standard. This is not a + problem, but does prompt the warning. + + + After installing each package, delete its source and build + directories, unless specifically instructed otherwise. Deleting the + sources prevents mis-configuration when the same package is reinstalled + later. + + + + + Check one last time that the LFS environment variable + is set up properly: + +echo $LFS + + Make sure the output shows the path to the LFS partition's mount + point, which is /mnt/lfs, using our + example. + + + + + Finally, one last important item must be emphasized: + + + Before issuing the build instructions for a package, the package + should be unpacked as user lfs, + and a cd into the created directory should be + performed. The build instructions assume that the + bash shell is in use. + + + + + + diff --git a/chapter05/introduction.xml b/chapter05/introduction.xml index 5e6a17119..33a566877 100644 --- a/chapter05/introduction.xml +++ b/chapter05/introduction.xml @@ -10,7 +10,7 @@ Introduction - This chapter shows how to compile and install a minimal Linux system. + This chapter shows how to build a minimal Linux system. This system will contain just enough tools to start constructing the final LFS system in and allow a working environment with more user convenience than a minimum environment would. @@ -26,42 +26,4 @@ production directories. Since the packages compiled here are temporary, we do not want them to pollute the soon-to-be LFS system. - - Before issuing the build instructions for a package, the package - should be unpacked as user lfs, - and a cd into the created directory should be performed. - The build instructions assume that the bash shell is - in use. - - - Several of the packages are patched before compilation, but only when - the patch is needed to circumvent a problem. A patch is often needed in both - this and the next chapter, but sometimes in only one or the other. Therefore, - do not be concerned if instructions for a downloaded patch seem to be missing. - Warning messages about offset or fuzz - may also be encountered when applying a patch. Do not worry about these - warnings, as the patch was still successfully applied. - - During the compilation of most packages, there will be several warnings - that scroll by on the screen. These are normal and can safely be ignored. - These warnings are as they appear—warnings about deprecated, but not - invalid, use of the C or C++ syntax. C standards change fairly often, and - some packages still use the older standard. This is not a problem, but does - prompt the warning. - - - After installing each package, delete its source and build directories, - unless specifically instructed otherwise. Deleting the sources prevents - mis-configuration when the same package is reinstalled later. - - - Check one last time that the LFS environment - variable is set up properly: - -echo $LFS - - Make sure the output shows the path to the LFS partition's mount - point, which is /mnt/lfs, using - our example. - -- cgit v1.2.3-54-g00ecf