diff options
| author | Pierre Labastie <pieere@linuxfromscratch.org> | 2020-06-17 20:50:25 +0000 |
|---|---|---|
| committer | Pierre Labastie <pieere@linuxfromscratch.org> | 2020-06-17 20:50:25 +0000 |
| commit | 12fff1eb8d1c5dcf9c4049d0d08f315d1103787a (patch) | |
| tree | a43e983a2e8b0e6b26e28b229b8dab744012a7ec /part3intro/introduction.xml | |
| parent | 450e8ac1abb969245e9889493fb09405a55f337c (diff) | |
Slightly change the layout in part III, so that the preliminary material
appear separated. Minor rewrites for accounting for the new layout
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11949 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'part3intro/introduction.xml')
| -rw-r--r-- | part3intro/introduction.xml | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/part3intro/introduction.xml b/part3intro/introduction.xml new file mode 100644 index 000000000..6d30ffe49 --- /dev/null +++ b/part3intro/introduction.xml @@ -0,0 +1,34 @@ +<?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-part3intro-intro"> + <?dbhtml filename="introduction.html"?> + + <title>Introduction</title> + + <para>This part is divided into three stages: first building a cross + compiler and its associated libraries; second, use this cross toolchain + to build several utilities in a way that isolates them from the host + distribution; third, enter the chroot environment, which further improves + host isolation, and build the remaining tools needed to build the final + system.</para> + + <important><para>With this part begins the real work of building a new + system. It requires much care in ensuring that the instructions are + followed exactly as the book shows them. You should try to understand + what they do, and whatever your eagerness to finish your build, you should + refrain from blindly type them as shown, but rather read documentation when + there is something you do not understand. Also, keep track of your typing + and of the output of commands, by sending them to a file, using the + <command>tee</command> utility. This allows for better diagnosing + if something gets wrong.</para></important> + + <para>The next section gives a technical introduction to the build process, + while the following one contains <emphasis role="strong">very + important</emphasis> general instructions.</para> + +</sect1> |