Ignore:
Timestamp:
10/01/2022 10:30:12 PM (21 months ago)
Author:
Thomas Trepl (Moody) <thomas@…>
Branches:
multilib
Children:
f3b2f16
Parents:
f29824e (diff), 4349661 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Automatic merge of trunk into multilib

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter04/settingenviron.xml

    rf29824e rc093e6b  
    2020EOF</userinput></screen>
    2121
    22   <para>When logged on as user <systemitem class="username">lfs</systemitem>,
    23   the initial shell is usually a <emphasis>login</emphasis> shell which reads
     22  <para>When logged on as user <systemitem class="username">lfs</systemitem>
     23  or switched to the &lfs-user; user using a <command>su</command> command
     24  with <quote><parameter>-</parameter></quote> option,
     25  the initial shell is a <emphasis>login</emphasis> shell which reads
    2426  the <filename>/etc/profile</filename> of the host (probably containing some
    2527  settings and environment variables) and then <filename>.bash_profile</filename>.
     
    3335
    3436  <para>The new instance of the shell is a <emphasis>non-login</emphasis>
    35   shell, which does not read, and execute, the contents of <filename>/etc/profile</filename> or
     37  shell, which does not read, and execute, the contents of the <filename>/etc/profile</filename> or
    3638  <filename>.bash_profile</filename> files, but rather reads, and executes, the
    3739  <filename>.bashrc</filename> file instead. Create the
     
    7476  <command>bash</command>'s hash function. Hashing is ordinarily a useful
    7577  feature&mdash;<command>bash</command> uses a hash table to remember the
    76   full path of executable files to avoid searching the <envar>PATH</envar>
     78  full path to executable files to avoid searching the <envar>PATH</envar>
    7779  time and again to find the same executable. However, the new tools should
    78   be used as soon as they are installed. By switching off the hash function,
    79   the shell will always search the <envar>PATH</envar> when a program is to
     80  be used as soon as they are installed. Switching off the hash function forces
     81  the shell to search the <envar>PATH</envar> whenever a program is to
    8082  be run. As such, the shell will find the newly compiled tools in
    8183  <filename class="directory">$LFS/tools/bin</filename> as soon as they are
     
    130132      <term><parameter>PATH=/usr/bin</parameter></term>
    131133      <listitem>
    132   <para>Many modern linux distributions have merged <filename
     134  <para>Many modern Linux distributions have merged <filename
    133135  class="directory">/bin</filename> and <filename
    134136  class="directory">/usr/bin</filename>. When this is the case, the standard
    135   <envar>PATH</envar> variable needs just to be set to <filename
     137  <envar>PATH</envar> variable should be set to <filename
    136138  class="directory">/usr/bin/</filename> for the <xref
    137139  linkend="chapter-temporary-tools"/> environment. When this is not the
     
    156158  of <xref linkend="chapter-cross-tools"/> is picked up by the shell
    157159  immediately after its installation. This, combined with turning off hashing,
    158   limits the risk that the compiler from the host be used instead of the
     160  limits the risk that the compiler from the host is used instead of the
    159161  cross-compiler.</para>
    160162      </listitem>
     
    210212
    211213  <para>Finally, to have the environment fully prepared for building the
    212   temporary tools, source the just-created user profile:</para>
     214  temporary tools, force the <command>bash</command> shell to read
     215  the new user profile:</para>
    213216
    214217<screen><userinput>source ~/.bash_profile</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.