source: prologue/architecture.xml@ f8f349e

Last change on this file since f8f349e was f8f349e, checked in by Xi Ruoyao <xry111@…>, 11 months ago

cross-ng: remove the restriction on the architecture of the host distro in prologue

  • Property mode set to 100644
File size: 2.1 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
8<sect1 id="pre-architecture">
9 <?dbhtml filename="architecture.html"?>
11 <title>LFS Target Architectures</title>
13<para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
14and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are
15also known to work, with some modifications, with the Power PC and ARM
18<para>For building LFS, the gain of building on a 64-bit system
19compared to a 32-bit system is minimal.
20For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system,
21using 4 cores, the following statistics were measured:</para>
23<screen><computeroutput>Architecture Build Time Build Size
2432-bit 239.9 minutes 3.6 GB
2564-bit 233.2 minutes 4.4 GB</computeroutput></screen>
27<para>As you can see, on the same hardware, the 64-bit build is only 3% faster
28and is 22% larger than the 32-bit build. If you plan to use LFS as a LAMP
29server, or a firewall, a 32-bit CPU may be largely sufficient. On the other
30hand, several packages in BLFS now need more than 4GB of RAM to be built
31and/or to run, so that if you plan to use LFS as a desktop, the LFS authors
32recommend building on a 64-bit system.</para>
34<para>The default 64-bit build that results from LFS is considered a
35<quote>pure</quote> 64-bit system. That is, it supports 64-bit executables
36only. Building a <quote>multi-lib</quote> system requires compiling many
37applications twice, once for a 32-bit system and once for a 64-bit system.
38This is not directly supported in LFS because it would interfere with the
39educational objective of providing the instructions needed for a
40straightforward base Linux system. Some LFS/BLFS editors maintain a fork
41of LFS for multilib, which is accessible at <ulink
42url=""/>. But it
43is an advanced topic.</para>
Note: See TracBrowser for help on using the repository browser.