source: prologue/architecture.xml@ 8988b94

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 8988b94 was 8988b94, checked in by Bruce Dubbs <bdubbs@…>, 15 years ago

Added a section to the Preface about LFS supported architectures

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9065 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.4 KB
Line 
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
13<para>The primary target architecture of LFS is the 32-bit Intel CPU. If you
14have not built an LFS system before, you should probably start with that
15target. The 32-bit architecture is the most widely supported Linux system and
16is most compatible with both open source and proprietary software.</para>
17
18<para>On the other hand, the instructions in this book are known to work, with
19some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a
20system that utilizes these CPUs, the main prerequsite in addition to those on
21the next few pages, is an existing system such as an earlier LFS system,
22Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets the system
23that you have. Also note that a 32-bit system can be installed and used as a
24host system on a 64-bit AMD/Intel system.</para>
25
26<para>If you decide to target a 64-bit AMD/Intel system, LFS does have some
27limitations. First, it does not currently provide instructions for a 64-bit
28boot loader. If there is an existing boot loader, it can be used to boot to
29any LFS system you build, but <xref linkend="ch-bootable-grub"/> cannot be
30built on a 64-bit system.</para>
31
32<para>Some other facts about a 64-bit systems need to be added here. When
33compared to a 32-bit system, the sizes of executable programs are slightly
34larger and the execution speeds are only slightly faster. For example, in a
35test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics
36were measured:</para>
37
38<screen><computeroutput>Architecture Build Time Build Size
3932-bit 198.5 minutes 648 MB
4064-bit 190.6 minutes 709 MB</computeroutput></screen>
41
42<para>As you can see, the 64-bit build is only 4% faster and is 9% larger than
43the 32-bit build. The gain from going to a 64-bit system is relatively
44minimal. Of course, if you have more than 4GB of RAM or want to manipulate
45data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para>
46
47<para>The default 64-bit build that results from LFS is considered a "pure"
4864-bit system. That is, it supports 64-bit executables only. Building a
49"multi-lib" system requires building many applications twice, once for a 32-bit
50system and once for a 64-bit system. Currently this is not directly supported
51in the book, but is under consideration for a future release. In the meantime,
52you can refer to the <ulink url="http://trac.cross-lfs.org/">Cross Linux From
53Scratch</ulink> project for this advanced topic.</para>
54
55<para>There is one last comment about 64-bit systems. There are some packages
56that cannot currently be built in a "pure" 64-bit system or require specialized
57build instructions. Generally, these packages have some embedded 32-bit
58specific assembly language instructions that fail when building on a 64-bit
59system. Examples include the <ulink
60url="http://www.linuxfromscratch.org/blfs/view/cvs/">Beyond Linux From Scratch
61(BLFS)</ulink> packages Zip and some Xorg drivers. Many of these problems can
62be worked around, but may require some specialized procedures or
63patches.</para>
64
65</sect1>
66
Note: See TracBrowser for help on using the repository browser.