source: prologue/architecture.xml@ 61707b1

11.0 11.0-rc1 11.0-rc2 11.0-rc3 ml-11.0 multilib trunk xry111/glibc-2.34 xry111/tester-nohack xry111/usr-move
Last change on this file since 61707b1 was 61707b1, checked in by Xi Ruoyao <xry111@…>, 9 months ago

secure LFS URL

  • Property mode set to 100644
File size: 2.4 KB
RevLine 
[8988b94]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="pre-architecture">
9 <?dbhtml filename="architecture.html"?>
10
11 <title>LFS Target Architectures</title>
12
[14377f4]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
[e043985]15also known to work, with some modifications, with the Power PC and ARM CPUs. To
16build a system that utilizes one of these CPUs, the main prerequisite, in
[394dc3fc]17addition to those on the next page, is an existing Linux system such as an
[e043985]18earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution
19that targets the architecture that you have. Also note that a 32-bit
20distribution can be installed and used as a host system on a 64-bit AMD/Intel
21computer.</para>
[c6d5b092]22
[394dc3fc]23<para>For building LFS, the gain of building on a 64-bit system
24compared to a 32-bit system is minimal.
25For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system,
26using 4 cores, the following statistics were measured:</para>
[8988b94]27
[2ca8941]28<screen><computeroutput>Architecture Build Time Build Size
[394dc3fc]2932-bit 239.9 minutes 3.6 GB
3064-bit 233.2 minutes 4.4 GB</computeroutput></screen>
31
32<para>As you can see, on the same hardware, the 64-bit build is only 3% faster
33and is 22% larger than the 32-bit build. If you plan to use LFS as a LAMP
34server, or a firewall, a 32-bit CPU may be largely sufficient. On the other
[493d6b5]35hand, several packages in BLFS now need more than 4GB of RAM to be built
[394dc3fc]36and/or to run, so that if you plan to use LFS as a desktop, the LFS authors
37recommend building on a 64-bit system.</para>
38
39<para>The default 64-bit build that results from LFS is considered a
40<quote>pure</quote> 64-bit system. That is, it supports 64-bit executables
41only. Building a <quote>multi-lib</quote> system requires compiling many
42applications twice, once for a 32-bit system and once for a 64-bit system.
43This is not directly supported in LFS because it would interfere with the
44educational objective of providing the instructions needed for a
45straightforward base Linux system. Some LFS/BLFS editors maintain a fork
46of LFS for multilib, which is accessible at <ulink
[61707b1]47url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But it
[394dc3fc]48is an advanced topic.</para>
[8988b94]49
50</sect1>
Note: See TracBrowser for help on using the repository browser.