mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-01-19 21:49:13 +00:00
2e7ca50f24
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9288 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
90 lines
3.4 KiB
XML
90 lines
3.4 KiB
XML
<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
<!ENTITY % general-entities SYSTEM "../general.ent">
|
|
%general-entities;
|
|
]>
|
|
|
|
<sect1 id="ch-tools-generalinstructions">
|
|
<?dbhtml filename="generalinstructions.html"?>
|
|
|
|
<title>General Compilation Instructions</title>
|
|
|
|
<para>When building packages there are several assumptions made within
|
|
the instructions:</para>
|
|
|
|
<itemizedlist>
|
|
|
|
<listitem>
|
|
<para>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 <emphasis>offset</emphasis> or
|
|
<emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do
|
|
not worry about these warnings, as the patch was still successfully
|
|
applied.</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>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.</para>
|
|
|
|
<important>
|
|
<para>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.</para>
|
|
</important>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>Check one last time that the <envar>LFS</envar> environment variable
|
|
is set up properly:</para>
|
|
|
|
<screen role="nodump"><userinput>echo $LFS</userinput></screen>
|
|
|
|
<para>Make sure the output shows the path to the LFS partition's mount
|
|
point, which is <filename class="directory">/mnt/lfs</filename>, using our
|
|
example.</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Finally, two last important items must be emphasized:</para>
|
|
|
|
<important>
|
|
<para>The build instructions assume that the <command>bash</command>
|
|
shell is in use.</para>
|
|
</important>
|
|
|
|
<important>
|
|
<para>Before issuing the build instructions for a package, the package
|
|
should be unpacked as user <systemitem class="username">lfs</systemitem>,
|
|
and a <command>cd</command> into the created directory should be
|
|
performed.</para>
|
|
</important>
|
|
</listitem>
|
|
|
|
</itemizedlist>
|
|
|
|
<para>To re-emphasize the build process:</para>
|
|
|
|
<screen role="nodump">
|
|
1. Place all the sources and patches in a directory that will be accessible from the
|
|
chroot envronment such as /mnt/lfs/sources/. Do <emphasis>not</emphasis> put sources in /mnt/lfs/tools/.
|
|
2. Change to the sources directory.
|
|
3. For each package:
|
|
a. Using the tar program, extract the package to be built.
|
|
b. Change to the directory created when the package was extracted.
|
|
c. Follow the book's instructions for building the package.
|
|
d. Change back to the sources directory.
|
|
e. Delete the extracted source directory and any <package>-build
|
|
directories that were created in the build process.</screen>
|
|
|
|
</sect1>
|