Changeset 3cf0fef
- Timestamp:
- 01/03/2003 02:33:13 AM (21 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.0, 6.1, 6.1.1, 6.3, 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, v4_1, v5_0, v5_1, v5_1_1, 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:
- 4d51529
- Parents:
- fa7b512
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/introduction.xml
rfa7b512 r3cf0fef 18 18 package is given right after the installation instructions.</para> 19 19 20 <para>Many of our packages must be patched before they can be compiled. 21 We only apply patches when and where they are needed. So, don't fret if 22 it seems like instructions for a patch are missing.</para> 20 <para>Several of the packages are patched before compilation, but only when 21 the patch is needed to circumvent a problem. Often the patch is needed in 22 both this and the next chapter, but sometimes in only one of them. So, don't 23 worry when instructions for a downloaded patch seem to be missing.</para> 23 24 24 <para>During the installation of several packages you will probably25 <para>During the installation of most packages you will 25 26 see all kinds of compiler warnings scroll by on your screen. These are 26 27 normal and can be safely ignored. They are just what they say they are: … … 29 30 packages still use the older standard, which is not really a problem.</para> 30 31 31 <para>Before you start, make sure the LFS environment variable is set up32 properly if you decided to make use of it. Runthe following:</para>32 <para>Before continuing, make sure the LFS environment variable is set up 33 properly (if you decided to make use of it) by executing the following:</para> 33 34 34 35 <para><screen><userinput>echo $LFS</userinput></screen></para> 35 36 36 <para>Check to make sure the output contains the correct directory to the LFS 37 partition's mount point (/mnt/lfs for example).</para> 37 <para>Make sure the output shows the path to your LFS partition's mount 38 point, which is <filename class="directory">/mnt/lfs</filename> if you 39 followed our example.</para> 38 40 39 41 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.