mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-03-06 06:14:47 +00:00
applied alex' intro cleanup patch
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2272 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
fa7b512907
commit
3cf0fef1de
@ -17,24 +17,26 @@ exactly what each package is used for, and why the user or the system
|
|||||||
needs it. For this purpose a short description of the content of each
|
needs it. For this purpose a short description of the content of each
|
||||||
package is given right after the installation instructions.</para>
|
package is given right after the installation instructions.</para>
|
||||||
|
|
||||||
<para>Many of our packages must be patched before they can be compiled.
|
<para>Several of the packages are patched before compilation, but only when
|
||||||
We only apply patches when and where they are needed. So, don't fret if
|
the patch is needed to circumvent a problem. Often the patch is needed in
|
||||||
it seems like instructions for a patch are missing.</para>
|
both this and the next chapter, but sometimes in only one of them. So, don't
|
||||||
|
worry when instructions for a downloaded patch seem to be missing.</para>
|
||||||
|
|
||||||
<para>During the installation of several packages you will probably
|
<para>During the installation of most packages you will
|
||||||
see all kinds of compiler warnings scroll by on your screen. These are
|
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:
|
normal and can be safely ignored. They are just what they say they are:
|
||||||
warnings -- mostly about improper, but not illegal, use of the C or C++
|
warnings -- mostly about improper, but not illegal, use of the C or C++
|
||||||
syntax. It's just that C standards have changed rather often and some
|
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.</para>
|
packages still use the older standard, which is not really a problem.</para>
|
||||||
|
|
||||||
<para>Before you start, make sure the LFS environment variable is set up
|
<para>Before continuing, make sure the LFS environment variable is set up
|
||||||
properly if you decided to make use of it. Run the following:</para>
|
properly (if you decided to make use of it) by executing the following:</para>
|
||||||
|
|
||||||
<para><screen><userinput>echo $LFS</userinput></screen></para>
|
<para><screen><userinput>echo $LFS</userinput></screen></para>
|
||||||
|
|
||||||
<para>Check to make sure the output contains the correct directory to the LFS
|
<para>Make sure the output shows the path to your LFS partition's mount
|
||||||
partition's mount point (/mnt/lfs for example).</para>
|
point, which is <filename class="directory">/mnt/lfs</filename> if you
|
||||||
|
followed our example.</para>
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user