Changes in prologue/architecture.xml [e43d96fa:7152faa]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
prologue/architecture.xml
re43d96fa r7152faa 11 11 <title>LFS Target Architectures</title> 12 12 13 <para>The primary target architectures of this LFS edition are the little 14 endian MIPS64 release 2 to 5 CPUs (the release 6 is not backward-compatible 15 with earlier releases). On the other hand, the instructions 16 in this book are also known to work, with some modifications, for 17 MIPS CPUs with a different byte order, word size, or ISA version. To 13 <para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit) 14 and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are 15 also known to work, with some modifications, with the Power PC and ARM CPUs. To 18 16 build a system that utilizes one of these alternative CPUs, the main prerequisite, in 19 17 addition to those on the next page, is an existing Linux system such as an 20 18 earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or some other distribution 21 that targets that architecture.</para> 19 that targets that architecture. (Note that a 32-bit 20 distribution can be installed and used as a host system on a 64-bit AMD/Intel 21 computer.)</para> 22 22 23 <para>There are three widely-used ABIs for 64-bit MIPS programs. 24 The <quote>o32</quote> ABI is compatible with the ABI of the legacy 32-bit 25 MIPS programs and it's used for running those legacy 32-bit programs on a 26 64-bit MIPS CPU. The <quote>n64</quote> ABI is designed for taking the full 27 advantage of 64-bit capability. The <quote>n32</quote> ABI is similar to 28 n64 but using 32-bit pointers, mainly used for 64-bit devices with a small 29 amount of RAM. The default 64-bit build that results from LFS is a 30 <quote>pure</quote> n64 system. That is, it supports n64 executables 23 <para>The gain from building on a 64-bit system, as 24 compared to a 32-bit system, is minimal. 25 For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system, 26 using 4 cores, the following statistics were measured:</para> 27 28 <screen><computeroutput>Architecture Build Time Build Size 29 32-bit 239.9 minutes 3.6 GB 30 64-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 33 (and 22% larger) than the 32-bit build. If you plan to use LFS as a LAMP 34 server, or a firewall, a 32-bit CPU may be good enough. On the other 35 hand, several packages in BLFS now need more than 4 GB of RAM to be built 36 and/or to run; if you plan to use LFS as a desktop, the LFS authors 37 recommend building a 64-bit system.</para> 38 39 <para>The default 64-bit build that results from LFS is a 40 <quote>pure</quote> 64-bit system. That is, it supports 64-bit executables 31 41 only. Building a <quote>multi-lib</quote> system requires compiling many 32 applications multiple times, each time for an ABI to be supported.42 applications twice, once for a 32-bit system and once for a 64-bit system. 33 43 This is not directly supported in LFS because it would interfere with the 34 44 educational objective of providing the minimal instructions needed for a … … 36 46 of LFS, accessible at <ulink 37 47 url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But 38 it's for x86_64, and anyway multilib is an advanced topic.</para>48 that's an advanced topic.</para> 39 49 40 50 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.