gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-07-12 07:14:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

Reword paragraph in 'Target Architectures' discussing multi-lib systems

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9174 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2010-01-31 22:21:06 +00:00
parent 8c264a8e02
commit cbd8a1a2bd
3 changed files with 19 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
chapter01/changelog.xml
View File

@ -37,6 +37,16 @@
--> -->
<listitem>
<para>2010-01-31</para>
<itemizedlist>
<listitem>
<para>[bdubbs] Reword paragraph in 'Target Architectures'
discussing multi-lib systems.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem> <listitem>
<para>2010-01-28</para> <para>2010-01-28</para>
<itemizedlist> <itemizedlist>

4
general.ent
View File

@ -1,5 +1,5 @@
<!ENTITY version "SVN-20100128"> <!ENTITY version "SVN-20100131">
<!ENTITY releasedate "January 28, 2010"> <!ENTITY releasedate "January 31, 2010">
<!ENTITY copyrightdate "1999-2010"><!-- jhalfs needs a literal dash, not &ndash; --> <!ENTITY copyrightdate "1999-2010"><!-- jhalfs needs a literal dash, not &ndash; -->
<!ENTITY milestone "7.0"> <!ENTITY milestone "7.0">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" --> <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->

13
prologue/architecture.xml
View File

@ -40,11 +40,12 @@ data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para>
<para>The default 64-bit build that results from LFS is considered a "pure" <para>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 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 "multi-lib" system requires compiling many applications twice, once for a
system and once for a 64-bit system. Currently this is not directly supported 32-bit system and once for a 64-bit system. This is not directly supported in
in the book, but is under consideration for a future release. In the meantime, LFS becuase it would interfere with the educational objective of providing the
you can refer to the <ulink url="http://trac.cross-lfs.org/">Cross Linux From instructions needed for a straight forward base Linux system. You can refer to
Scratch</ulink> project for this advanced topic.</para> the <ulink url="http://trac.cross-lfs.org/">Cross Linux From Scratch</ulink>
project for this advanced topic.</para>
<para>There is one last comment about 64-bit systems. There are some packages <para>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 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 specific assembly language instructions that fail when building on a 64-bit
system. Examples include the <ulink system. Examples include the <ulink
url="http://www.linuxfromscratch.org/blfs/view/svn/">Beyond Linux From Scratch url="http://www.linuxfromscratch.org/blfs/view/svn/">Beyond Linux From Scratch
(BLFS)</ulink> packages Zip and some Xorg drivers. Many of these problems can (BLFS)</ulink> some Xorg drivers. Many of these problems can
be worked around, but may require some specialized procedures or be worked around, but may require some specialized procedures or
patches.</para> patches.</para>