source: prologue/architecture.xml@ a02b8ef

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 7.10 7.10-rc1 7.7 7.7-rc1 7.8 7.8-rc1 7.9 7.9-rc1 7.9-rc2 8.0 8.0-rc1 8.1 8.1-rc1 8.1-rc2 8.2 8.2-rc1 8.3 8.3-rc1 8.3-rc2 8.4 8.4-rc1 9.0 9.0-rc1 9.1 9.1-rc1 BOOK.old cross-chap5 ml-11.0 multilib nosym old-trunk trunk xry111/git-transition xry111/glibc-2.34 xry111/tester-nohack xry111/usr-move
Last change on this file since a02b8ef was a02b8ef, checked in by Bruce Dubbs <bdubbs@…>, 7 years ago

Update to man-pages-3.76.
Fix URL for CLFS.
Update copyright year.
Make version-check script more robust.

git-svn-id: 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.9 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 CPUs. To
16build a system that utilizes one of these CPUs, the main prerequisite, in
17addition to those on the next few pages, is an existing Linux system such as an
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
23<para>Some other facts about 64-bit systems need to be added here. When
24compared to a 32-bit system, the sizes of executable programs are slightly
25larger and the execution speeds are only slightly faster. For example, in a
26test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics
27were measured:</para>
29<screen><computeroutput>Architecture Build Time Build Size
3032-bit 198.5 minutes 648 MB
3164-bit 190.6 minutes 709 MB</computeroutput></screen>
33<para>As you can see, the 64-bit build is only 4% faster and is 9% larger than
34the 32-bit build. The gain from going to a 64-bit system is relatively
35minimal. Of course, if you have more than 4GB of RAM or want to manipulate
36data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para>
38<para>The default 64-bit build that results from LFS is considered a "pure"
3964-bit system. That is, it supports 64-bit executables only. Building a
40"multi-lib" system requires compiling many applications twice, once for a
4132-bit system and once for a 64-bit system. This is not directly supported in
42LFS because it would interfere with the educational objective of providing the
43instructions needed for a straightforward base Linux system. You can refer to
44the <ulink url="">Cross Linux From Scratch</ulink>
45project for this advanced topic.</para>
47<para>There is one last comment about 64-bit systems. There are some older
48packages that cannot currently be built in a "pure" 64-bit system or require
49specialized build instructions. Generally, these packages have some embedded
5032-bit specific assembly language instructions that fail when building on a
5164-bit system. This includes some Xorg drivers for some legacy video cards at
52<ulink url="">
53</ulink>. Many of these
54problems can be worked around, but may require some specialized procedures or
Note: See TracBrowser for help on using the repository browser.