| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
 | 
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 | 
|---|
| 3 |   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
 | 
|---|
| 4 |   <!ENTITY % general-entities SYSTEM "../../general.ent">
 | 
|---|
| 5 |   %general-entities;
 | 
|---|
| 6 | ]>
 | 
|---|
| 7 | 
 | 
|---|
| 8 | <sect1 id="ch-intro-how">
 | 
|---|
| 9 |   <?dbhtml filename="how.html"?>
 | 
|---|
| 10 | 
 | 
|---|
| 11 |   <title>How to Build a CLFS System</title>
 | 
|---|
| 12 | 
 | 
|---|
| 13 |   <para>The CLFS system will be built by using a previously installed
 | 
|---|
| 14 |   Unix system or Linux distribution (such as Debian, Fedora, openSUSE,
 | 
|---|
| 15 |   or Ubuntu). This existing system (the host) will be used as a starting
 | 
|---|
| 16 |   point to provide necessary programs, including a compiler, linker, and shell,
 | 
|---|
| 17 |   to build the new system. Select the <quote>development</quote> option
 | 
|---|
| 18 |   during the distribution installation to be able to access these
 | 
|---|
| 19 |   tools.</para>
 | 
|---|
| 20 | 
 | 
|---|
| 21 |   <para>As an alternative to installing an entire separate distribution onto
 | 
|---|
| 22 |   your machine, you may wish to use a livecd. Most distributions provide
 | 
|---|
| 23 |   a livecd, which provides an environment to which you can add the required
 | 
|---|
| 24 |   tools onto, allowing you to successfully follow the instructions in this
 | 
|---|
| 25 |   book. Remember that if you reboot the livecd you will need to reconfigure
 | 
|---|
| 26 |   the host environment before continuing with your build.</para>
 | 
|---|
| 27 | 
 | 
|---|
| 28 |   <para><xref linkend="chapter-partitioning"/> of this book describes how
 | 
|---|
| 29 |   to create a new Linux native partition and file system, the place
 | 
|---|
| 30 |   where the new CLFS system will be compiled and installed. <xref
 | 
|---|
| 31 |   linkend="chapter-getting-materials"/> explains which packages and
 | 
|---|
| 32 |   patches need to be downloaded to build a CLFS system and how to store
 | 
|---|
| 33 |   them on the new file system. <xref linkend="chapter-final-preps"/>
 | 
|---|
| 34 |   discusses the setup for an appropriate working environment. Please read
 | 
|---|
| 35 |   <xref linkend="chapter-final-preps"/> carefully as it explains several
 | 
|---|
| 36 |   important issues the developer should be aware of before beginning to
 | 
|---|
| 37 |   work through <xref linkend="chapter-cross-tools"/> and
 | 
|---|
| 38 |   beyond.</para>
 | 
|---|
| 39 | 
 | 
|---|
| 40 |   <para><xref linkend="chapter-cross-tools"/> explains the installation of
 | 
|---|
| 41 |   cross-compile tools which will be built on the host but be able to compile
 | 
|---|
| 42 |   programs that run on the target machine. These cross-compile tools will
 | 
|---|
| 43 |   be used to create a temporary, minimal system that will be the basis for
 | 
|---|
| 44 |   building the final CLFS system. Some of these packages are needed to resolve
 | 
|---|
| 45 |   circular dependencies—for example, to compile a compiler, you need a
 | 
|---|
| 46 |   compiler.</para>
 | 
|---|
| 47 | 
 | 
|---|
| 48 |   <para>The process of building cross-compile tools first involves building and
 | 
|---|
| 49 |   installing all the necessary tools to create a build system for the target
 | 
|---|
| 50 |   machine. With these cross-compiled tools, we eliminate any
 | 
|---|
| 51 |   dependencies on the toolchain from our host distro.</para>
 | 
|---|
| 52 | 
 | 
|---|
| 53 |   <para>After we build our <quote>Cross-Tools</quote>, we start building
 | 
|---|
| 54 |   a very minimal working system in
 | 
|---|
| 55 |   <filename class="directory">/tools</filename>, using the cross-toolchain in
 | 
|---|
| 56 |   <filename class="directory">/cross-tools</filename>. Once the temporary
 | 
|---|
| 57 |   system is finished, we perform a few additional tasks to prepare to
 | 
|---|
| 58 |   enter this temporary build environment, either by booting or chrooting into
 | 
|---|
| 59 |   it. For more details about the difference between these methods, see
 | 
|---|
| 60 |   <xref linkend="ch-temp-system-choose"/>.</para>
 | 
|---|
| 61 | 
 | 
|---|
| 62 |   <para>In <xref linkend="chapter-building-system"/>, after having booted
 | 
|---|
| 63 |   or chrooted into the temporary build environment, the full CLFS system is
 | 
|---|
| 64 |   built.</para>
 | 
|---|
| 65 | 
 | 
|---|
| 66 |   <para>To finish the installation, several configuration files are created in
 | 
|---|
| 67 |   <xref linkend="chapter-system-config"/>, and the kernel and boot loader are
 | 
|---|
| 68 |   set up in <xref linkend="chapter-bootable"/>.
 | 
|---|
| 69 |   <xref linkend="chapter-finalizing"/>
 | 
|---|
| 70 |   contains information on furthering the CLFS experience beyond this book.
 | 
|---|
| 71 |   After the steps in this book have been implemented, the computer will be
 | 
|---|
| 72 |   ready to reboot into the new CLFS system.</para>
 | 
|---|
| 73 | 
 | 
|---|
| 74 |   <para>This is the process in a nutshell. Detailed information on each
 | 
|---|
| 75 |   step is discussed in the following chapters and package descriptions.
 | 
|---|
| 76 |   Items that may seem complicated will be clarified, and everything will
 | 
|---|
| 77 |   fall into place as the reader embarks on the CLFS adventure.</para>
 | 
|---|
| 78 | 
 | 
|---|
| 79 | </sect1>
 | 
|---|