Changeset c093e6b for chapter04/settingenviron.xml
- Timestamp:
- 10/01/2022 10:30:12 PM (21 months ago)
- 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. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/settingenviron.xml
rf29824e rc093e6b 20 20 EOF</userinput></screen> 21 21 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 24 26 the <filename>/etc/profile</filename> of the host (probably containing some 25 27 settings and environment variables) and then <filename>.bash_profile</filename>. … … 33 35 34 36 <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> or37 shell, which does not read, and execute, the contents of the <filename>/etc/profile</filename> or 36 38 <filename>.bash_profile</filename> files, but rather reads, and executes, the 37 39 <filename>.bashrc</filename> file instead. Create the … … 74 76 <command>bash</command>'s hash function. Hashing is ordinarily a useful 75 77 feature—<command>bash</command> uses a hash table to remember the 76 full path ofexecutable files to avoid searching the <envar>PATH</envar>78 full path to executable files to avoid searching the <envar>PATH</envar> 77 79 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> whena program is to80 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 80 82 be run. As such, the shell will find the newly compiled tools in 81 83 <filename class="directory">$LFS/tools/bin</filename> as soon as they are … … 130 132 <term><parameter>PATH=/usr/bin</parameter></term> 131 133 <listitem> 132 <para>Many modern linux distributions have merged <filename134 <para>Many modern Linux distributions have merged <filename 133 135 class="directory">/bin</filename> and <filename 134 136 class="directory">/usr/bin</filename>. When this is the case, the standard 135 <envar>PATH</envar> variable needs just tobe set to <filename137 <envar>PATH</envar> variable should be set to <filename 136 138 class="directory">/usr/bin/</filename> for the <xref 137 139 linkend="chapter-temporary-tools"/> environment. When this is not the … … 156 158 of <xref linkend="chapter-cross-tools"/> is picked up by the shell 157 159 immediately after its installation. This, combined with turning off hashing, 158 limits the risk that the compiler from the host beused instead of the160 limits the risk that the compiler from the host is used instead of the 159 161 cross-compiler.</para> 160 162 </listitem> … … 210 212 211 213 <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> 213 216 214 217 <screen><userinput>source ~/.bash_profile</userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.