From cbd8a1a2bd88d0beefb7e56cc6059eb34ab92044 Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sun, 31 Jan 2010 22:21:06 +0000 Subject: Reword paragraph in 'Target Architectures' discussing multi-lib systems git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9174 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- prologue/architecture.xml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'prologue/architecture.xml') diff --git a/prologue/architecture.xml b/prologue/architecture.xml index aa8cb2399..032c1812b 100644 --- a/prologue/architecture.xml +++ b/prologue/architecture.xml @@ -40,11 +40,12 @@ data that exceeds 4GB, the advantages of a 64-bit system are substantial. The default 64-bit build that results from LFS is considered a "pure" 64-bit system. That is, it supports 64-bit executables only. Building a -"multi-lib" system requires compiling many applications twice, once for a 32-bit -system and once for a 64-bit system. Currently this is not directly supported -in the book, but is under consideration for a future release. In the meantime, -you can refer to the Cross Linux From -Scratch project for this advanced topic. +"multi-lib" 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 becuase it would interfere with the educational objective of providing the +instructions needed for a straight forward base Linux system. You can refer to +the Cross Linux From Scratch +project for this advanced topic. There is one last comment about 64-bit systems. There are some packages that cannot currently be built in a "pure" 64-bit system or require specialized @@ -52,7 +53,7 @@ build instructions. Generally, these packages have some embedded 32-bit specific assembly language instructions that fail when building on a 64-bit system. Examples include the Beyond Linux From Scratch -(BLFS) packages Zip and some Xorg drivers. Many of these problems can +(BLFS) some Xorg drivers. Many of these problems can be worked around, but may require some specialized procedures or patches. -- cgit v1.2.3-54-g00ecf