Ignore:
Timestamp:
06/03/2003 10:25:25 PM (21 years ago)
Author:
Gerard Beekmans <gerard@…>
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, 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:
592cfd6
Parents:
8f999de5
Message:

Applied Alex' "apapting-the-text.patch" patch

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2639 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/setting-environment.xml

    r8f999de5 r66e4325  
    11<sect1 id="ch05-settingenviron">
    22<title>Setting up the environment</title>
    3 <?dbhtml filename="settingenviron.html" dir="chapter05"?>
     3<?dbhtml filename="settingenvironment.html" dir="chapter05"?>
    44
    55<para>While logged in as user <emphasis>lfs</emphasis>, issue the
    … …  
    1414export LFS LC_ALL PATH
    1515EOF
     16
    1617source ~/.bash_profile</userinput></screen></para>
    1718
    18 <para><userinput>set +h</userinput> turns off Bash's hash function. Hash
    19 normally is a useful feature where Bash uses a hash table to remember the
    20 full pathnames of executable files to avoid multiple `PATH' searches.
    21 However, we'd like the new tools to become available as soon as they are
    22 installed.  By switching off the hash function, our "interactive" commands
    23 (make, patch, sed, cp and so forth) will always use the newest available
    24 during the build process.</para>
     19<para>The <userinput>set +h</userinput> command turns off
     20<userinput>bash</userinput>'s hash function. Normally hashing is a useful
     21feature: <userinput>bash</userinput> uses a hash table to remember the
     22full pathnames of executable files to avoid searching the PATH time and time
     23again to find the same executable. However, we'd like the new tools to be
     24used as soon as they are installed.  By switching off the hash function, our
     25"interactive" commands (<userinput>make</userinput>,
     26<userinput>patch</userinput>, <userinput>sed</userinput>,
     27<userinput>cp</userinput> and so forth) will always use
     28the newest available version during the build process.</para>
    2529
    26 <para>This profile sets the umask to 022, so newly created files and
    27 directories will have the correct permissions. To be more specific, only
    28 the file owner will have write permission to new files and directories.
    29 Other users of the system will be have read permission, and executable
    30 permission to directories. It is advisable to keep this setting throughout
    31 your LFS installation.</para>
    32 
     30<para>Setting the user file-creation mask to 022 ensures that newly created
     31files and directories are only writable for their owner, but readable and
     32executable for anyone.</para>
     33 
    3334<para>The LFS variable should of course be set to the mount point you
    3435chose.</para>
    … …  
    3738making their messages follow the conventions of a specified country. If your
    3839host system uses a version of <emphasis>glibc</emphasis> older than 2.2.4,
    39 having LC_ALL set to something other than "C" or "POSIX" during this chapter
     40having LC_ALL set to something other than "POSIX" or "C" during this chapter
    4041may cause trouble if you exit the chroot environment and wish to return later.
    41 By setting LC_ALL to "POSIX" ("C" is an alias for "POSIX") we ensure that
     42By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that
    4243everything will work as expected in the chroot environment.</para>
    4344
    44 <para>LDFLAGS is a variable we set in order to prevent debugging symbols from
    45 being compiled into our static packages. By omitting these symbols during
    46 the linking stage of compilation, we save hard drive space and decrease our
    47 build time.</para>
     45<para>We prepend <filename>/stage1/bin</filename> to the standard PATH so
     46that, as we move along through this chapter, the tools we build will get used
     47during the rest of the building process.</para>
    4848
    49 <para>We are now prepared to begin building the temporary tools which will
    50 support us in later chapters.</para>
     49<para>Now, after sourcing the just-created profile, we're all set to begin
     50building the temporary tools that will support us in later chapters.</para>
    5151
    5252</sect1>
Note: See TracChangeset for help on using the changeset viewer.