Changeset 460f575 for prologue

Timestamp:

02/25/2022 08:47:36 PM (2 years ago)

Author:

William Harrington <kb0iic@…>

Branches:

arm

Children:

9c0b35a

Parents:

b0a6b0c

Message:

Initial LFS-ARM book.

Location:

prologue

Files:

• architecture.xml (modified) (1 diff)
• bookinfo.xml (modified) (2 diffs)
• why.xml (modified) (1 diff)

prologue/architecture.xml

@@ -11 +11 @@
   <title>LFS Target Architectures</title>
 
-<para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
-and x86_64 (64-bit) CPUs.  On the other hand, the instructions in this book are
-also known to work, with some modifications, with the Power PC and ARM CPUs. To
-build a system that utilizes one of these CPUs, the main prerequisite, in
+<para>The primary target architectures of LFS-ARM are the ARM and ARM64 CPUs.
+For other ARCHs refer to the main LFS book or CLFS as a historical reference.
+To build a system that utilizes one of these CPUs, the main prerequisite, in
 addition to those on the next page, is an existing Linux system such as an
 earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution
 that targets the architecture that you have. Also note that a 32-bit
-distribution can be installed and used as a host system on a 64-bit AMD/Intel
-computer.</para>
-
-<para>For building LFS, the gain of building on a 64-bit system
-compared to a 32-bit system is minimal.
-For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system,
-using 4 cores, the following statistics were measured:</para>
-
-<screen><computeroutput>Architecture Build Time     Build Size
-32-bit       239.9 minutes  3.6 GB
-64-bit       233.2 minutes  4.4 GB</computeroutput></screen>
-
-<para>As you can see, on the same hardware, the 64-bit build is only 3% faster
-and is 22% larger than the 32-bit build. If you plan to use LFS as a LAMP
-server, or a firewall, a 32-bit CPU may be largely sufficient. On the other
-hand, several packages in BLFS now need more than 4GB of RAM to be built
-and/or to run, so that if you plan to use LFS as a desktop, the LFS authors
-recommend building on a 64-bit system.</para>
-
-<para>The default 64-bit build that results from LFS is considered a
-<quote>pure</quote> 64-bit system. That is, it supports 64-bit executables
-only. Building a <quote>multi-lib</quote> system requires compiling many
-applications twice, once for a 32-bit system and once for a 64-bit system.
-This is not directly supported in LFS because it would interfere with the
-educational objective of providing the instructions needed for a
-straightforward base Linux system. Some LFS/BLFS editors maintain a fork
-of LFS for multilib, which is accessible at <ulink
-url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But it
-is an advanced topic.</para>
+distribution can be installed and used as a host system on a 64-bit ARM
+unoptimized computer.</para>
 
 </sect1>

prologue/bookinfo.xml

@@ -30 +30 @@
       <surname>Lucas</surname>
     </author>
+
+    <author>
+      <firstname>Editor: William</firstname>
+      <surname>Harrington</surname>
+    </author>
+
   </authorgroup>
+
 
   <copyright id="copyright">
@@ -38 +45 @@
 
   <legalnotice>
-
-    <para>Copyright &copy; &copyrightdate;, Gerard Beekmans</para>
 
     <para>All rights reserved.</para>

prologue/why.xml

@@ -292 +292 @@
         <para>This package contains programs for basic and advanced IPv4 and
         IPv6 networking.  It was chosen over the other common network
-        tools package (net-tools) for its IPv6 capabilities.  </para>
+        tools package (net-tools) for its IPv6 capabilities.</para>
+      </listitem>
+
+      <listitem>
+        <para>ISL</para>
+
+        <para>This package provides a thread-safe C library for manipulating 
+        sets and relations of integer points bounded by affine constraints.
+        It is used as backend polyhedral library in the GCC Graphite framework
+        and in the LLVM Polly framework for loop optimizations.</para>
       </listitem>