architecture.xml 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758
  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. <sect1 id="pre-architecture">
  8. <?dbhtml filename="architecture.html"?>
  9. <title>LFS Target Architectures</title>
  10. <para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
  11. and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are
  12. also known to work, with some modifications, with the Power PC and ARM CPUs. To
  13. build a system that utilizes one of these CPUs, the main prerequisite, in
  14. addition to those on the next few pages, is an existing Linux system such as an
  15. earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution
  16. that targets the architecture that you have. Also note that a 32-bit
  17. distribution can be installed and used as a host system on a 64-bit AMD/Intel
  18. computer.</para>
  19. <para>Some other facts about 64-bit systems need to be added here. When
  20. compared to a 32-bit system, the sizes of executable programs are slightly
  21. larger and the execution speeds are only slightly faster. For example, in a
  22. test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics
  23. were measured:</para>
  24. <screen><computeroutput>Architecture Build Time Build Size
  25. 32-bit 198.5 minutes 648 MB
  26. 64-bit 190.6 minutes 709 MB</computeroutput></screen>
  27. <para>As you can see, the 64-bit build is only 4% faster and is 9% larger than
  28. the 32-bit build. The gain from going to a 64-bit system is relatively
  29. minimal. Of course, if you have more than 4GB of RAM or want to manipulate
  30. data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para>
  31. <para>The default 64-bit build that results from LFS is considered a "pure"
  32. 64-bit system. That is, it supports 64-bit executables only. Building a
  33. "multi-lib" system requires compiling many applications twice, once for a
  34. 32-bit system and once for a 64-bit system. This is not directly supported in
  35. LFS because it would interfere with the educational objective of providing the
  36. instructions needed for a straightforward base Linux system. You can refer to
  37. the <ulink url="http://trac.clfs.org/">Cross Linux From Scratch</ulink>
  38. project for this advanced topic.</para>
  39. <para>There is one last comment about 64-bit systems. There are some older
  40. packages that cannot currently be built in a "pure" 64-bit system or require
  41. specialized build instructions. Generally, these packages have some embedded
  42. 32-bit specific assembly language instructions that fail when building on a
  43. 64-bit system. This includes some Xorg drivers for some legacy video cards at
  44. <ulink url="http://xorg.freedesktop.org/releases/individual/driver/">
  45. http://xorg.freedesktop.org/releases/individual/driver/</ulink>. Many of these
  46. problems can be worked around, but may require some specialized procedures or
  47. patches.</para>
  48. </sect1>