|
|
@@ -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.</para>
|
|
|
|
|
|
-<para>The build instructions assume that you are using the
|
|
|
-<command>bash</command> shell. It is also expected that you have already
|
|
|
-unpacked a source package (while logged in as user <emphasis>lfs</emphasis> --
|
|
|
-explained shortly) and performed a <userinput>cd</userinput> into the source
|
|
|
-directory of a package before issuing its build commands.</para>
|
|
|
+<para>Before issuing the build instructions for a package you are expected to
|
|
|
+have already unpacked it as user <emphasis>lfs</emphasis> (explained shortly),
|
|
|
+and to have performed a <userinput>cd</userinput> into the created directory.
|
|
|
+The build instructions assume that you are using the <command>bash</command>
|
|
|
+shell.</para>
|
|
|
|
|
|
<para>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
|
|
|
<emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>. These warnings are
|
|
|
-nothing to worry about as the patch was still successfully applied.</para>
|
|
|
-
|
|
|
-<para>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.</para>
|
|
|
-
|
|
|
-<para><emphasis>Unless</emphasis> told not to, you should normally delete the
|
|
|
-source and build directories after installing each package -- for cleanness
|
|
|
-sake and to save space.</para>
|
|
|
-
|
|
|
-<para>Before continuing, make sure the LFS environment variable is set up
|
|
|
-properly by executing the following:</para>
|
|
|
+nothing to worry about, as the patch was still successfully applied.</para>
|
|
|
+
|
|
|
+<para>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.</para>
|
|
|
+
|
|
|
+<para>After installing each package you should delete its source and build
|
|
|
+directories, <emphasis>unless</emphasis> 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.</para>
|
|
|
+
|
|
|
+<para>Now first check that your LFS environment variable is set up
|
|
|
+properly:</para>
|
|
|
|
|
|
<screen><userinput>echo $LFS</userinput></screen>
|
|
|
|
Alex Gronenwoud