Changeset 3c63868
- Timestamp:
- 10/26/2008 05:47:52 PM (16 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 3842a20
- Parents:
- 33d608d
- Files:
-
- 1 added
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r33d608d r3c63868 41 41 <itemizedlist> 42 42 <listitem> 43 <para>[bdubbs] - Added a General Compilation Instructions section 44 immediatley before binutils. Essentially reordered the presentation 45 that was in the Chapter 5 Introduction.</para> 46 </listitem> 47 <listitem> 43 48 <para>[bdubbs] - Remove unnecessary mandir patch. Updated 44 49 vim package contents.</para> -
chapter05/chapter05.xml
r33d608d r3c63868 14 14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="introduction.xml"/> 15 15 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="toolchaintechnotes.xml"/> 16 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="generalinstructions.xml"/> 16 17 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="binutils-pass1.xml"/> 17 18 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gcc-pass1.xml"/> -
chapter05/introduction.xml
r33d608d r3c63868 11 11 <title>Introduction</title> 12 12 13 <para>This chapter shows how to compile and installa minimal Linux system.13 <para>This chapter shows how to build a minimal Linux system. 14 14 This system will contain just enough tools to start constructing the final 15 15 LFS system in <xref linkend="chapter-building-system"/> and allow a working … … 27 27 we do not want them to pollute the soon-to-be LFS system.</para> 28 28 29 <important>30 <para>Before issuing the build instructions for a package, the package31 should be unpacked as user <systemitem class="username">lfs</systemitem>,32 and a <command>cd</command> into the created directory should be performed.33 The build instructions assume that the <command>bash</command> shell is34 in use.</para>35 </important>36 37 <para>Several of the packages are patched before compilation, but only when38 the patch is needed to circumvent a problem. A patch is often needed in both39 this and the next chapter, but sometimes in only one or the other. Therefore,40 do not be concerned if instructions for a downloaded patch seem to be missing.41 Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>42 may also be encountered when applying a patch. Do not worry about these43 warnings, as the patch was still successfully applied.</para>44 45 <para>During the compilation of most packages, there will be several warnings46 that scroll by on the screen. These are normal and can safely be ignored.47 These warnings are as they appear—warnings about deprecated, but not48 invalid, use of the C or C++ syntax. C standards change fairly often, and49 some packages still use the older standard. This is not a problem, but does50 prompt the warning.</para>51 52 <important>53 <para>After installing each package, delete its source and build directories,54 unless specifically instructed otherwise. Deleting the sources prevents55 mis-configuration when the same package is reinstalled later.</para>56 </important>57 58 <para>Check one last time that the <envar>LFS</envar> environment59 variable is set up properly:</para>60 61 <screen role="nodump"><userinput>echo $LFS</userinput></screen>62 63 <para>Make sure the output shows the path to the LFS partition's mount64 point, which is <filename class="directory">/mnt/lfs</filename>, using65 our example.</para>66 67 29 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.