Changeset c6d5b092 for prologue/architecture.xml
- Timestamp:
- 01/09/2010 07:15:55 AM (14 years ago)
- Branches:
- 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
- Children:
- a55f5b38
- Parents:
- 281a7d3
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
prologue/architecture.xml
r281a7d3 rc6d5b092 11 11 <title>LFS Target Architectures</title> 12 12 13 <para>The primary target architecture of LFS is the 32-bit Intel CPU. 13 <para>The primary target architecture of LFS is the 32-bit Intel CPU. If you 14 14 have not built an LFS system before, you should probably start with that 15 target. 15 target. The 32-bit architecture is the most widely supported Linux system and 16 16 is most compatible with both open source and proprietary software.</para> 17 17 18 18 <para>On the other hand, the instructions in this book are known to work, with 19 some modifications, with both Power PC and 64-bit AMD/Intel CPUs. 20 system that utilizes these CPUs, the main prerequisite in addition to those on21 th e next few pages, is an existing system such as an earlier LFS system,22 Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets the system 23 th at you have. Also note that a 32-bit system can be installed and used as a24 host system on a 64-bit AMD/Intel system.</para>19 some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a 20 system that utilizes one of these CPUs, the main prerequisite, in addition to 21 those on the next few pages, is an existing Linux system such as an earlier LFS 22 installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets 23 the architecture that you have. Also note that a 32-bit distribution can be 24 installed and used as a host system on a 64-bit AMD/Intel computer.</para> 25 25 26 <para>Some other facts about a 64-bit systems need to be added here. 26 <para>Some other facts about a 64-bit systems need to be added here. When 27 27 compared to a 32-bit system, the sizes of executable programs are slightly 28 larger and the execution speeds are only slightly faster. 28 larger and the execution speeds are only slightly faster. For example, in a 29 29 test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics 30 30 were measured:</para> … … 40 40 41 41 <para>The default 64-bit build that results from LFS is considered a "pure" 42 64-bit system. That is, it supports 64-bit executables only.Building a43 "multi-lib" system requires building many applications twice, once for a 32-bit44 system and once for a 64-bit system. 45 in the book, but is under consideration for a future release. 42 64-bit system. That is, it supports 64-bit executables only. Building a 43 "multi-lib" system requires compiling many applications twice, once for a 32-bit 44 system and once for a 64-bit system. Currently this is not directly supported 45 in the book, but is under consideration for a future release. In the meantime, 46 46 you can refer to the <ulink url="http://trac.cross-lfs.org/">Cross Linux From 47 47 Scratch</ulink> project for this advanced topic.</para> 48 48 49 <para>There is one last comment about 64-bit systems. 49 <para>There is one last comment about 64-bit systems. There are some packages 50 50 that cannot currently be built in a "pure" 64-bit system or require specialized 51 build instructions. 51 build instructions. Generally, these packages have some embedded 32-bit 52 52 specific assembly language instructions that fail when building on a 64-bit 53 53 system. Examples include the <ulink
Note:
See TracChangeset
for help on using the changeset viewer.