Changeset 7739ad3 for prologue/architecture.xml
- Timestamp:
- 10/15/2022 06:25:26 PM (2 years ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/update-glibc
- Children:
- 2e45b62
- Parents:
- e0ae8cb
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
prologue/architecture.xml
re0ae8cb r7739ad3 14 14 and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are 15 15 also known to work, with some modifications, with the Power PC and ARM CPUs. To 16 build a system that utilizes one of these CPUs, the main prerequisite, in16 build a system that utilizes one of these alternative CPUs, the main prerequisite, in 17 17 addition to those on the next page, is an existing Linux system such as an 18 earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution19 that targets th e architecture that you have. Also note that a 32-bit18 earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or some other distribution 19 that targets that architecture. (Note that a 32-bit 20 20 distribution can be installed and used as a host system on a 64-bit AMD/Intel 21 computer. </para>21 computer.)</para> 22 22 23 <para> For building LFS, the gain of building on a 64-bit system24 compared to a 32-bit system is minimal.23 <para>The gain from building on a 64-bit system, as 24 compared to a 32-bit system, is minimal. 25 25 For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system, 26 26 using 4 cores, the following statistics were measured:</para> … … 31 31 32 32 <para>As you can see, on the same hardware, the 64-bit build is only 3% faster 33 and is 22% largerthan the 32-bit build. If you plan to use LFS as a LAMP34 server, or a firewall, a 32-bit CPU may be largely sufficient. On the other35 hand, several packages in BLFS now need more than 4 GB of RAM to be built36 and/or to run , so thatif you plan to use LFS as a desktop, the LFS authors37 recommend building ona 64-bit system.</para>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 38 39 <para>The default 64-bit build that results from LFS is considereda39 <para>The default 64-bit build that results from LFS is a 40 40 <quote>pure</quote> 64-bit system. That is, it supports 64-bit executables 41 41 only. Building a <quote>multi-lib</quote> system requires compiling many 42 42 applications twice, once for a 32-bit system and once for a 64-bit system. 43 43 This is not directly supported in LFS because it would interfere with the 44 educational objective of providing the instructions needed for a45 straightforward base Linux system. Some LFS/BLFS editors maintain afork46 of LFS for multilib, which isaccessible at <ulink47 url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But it48 is an advanced topic.</para>44 educational objective of providing the minimal instructions needed for a 45 basic Linux system. Some of the LFS/BLFS editors maintain a multilib fork 46 of LFS, accessible at <ulink 47 url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But 48 that's an advanced topic.</para> 49 49 50 50 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.