Changeset dd61c77 for chapter04/settingenviron.xml
- Timestamp:
- 10/01/2022 08:03:20 AM (19 months ago)
- Branches:
- xry111/clfs-ng
- Children:
- ef1f48b
- Parents:
- 259794e (diff), 2bf32ff (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
r259794e rdd61c77 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 … … 60 62 <command>bash</command>'s hash function. Hashing is ordinarily a useful 61 63 feature—<command>bash</command> uses a hash table to remember the 62 full path ofexecutable files to avoid searching the <envar>PATH</envar>64 full path to executable files to avoid searching the <envar>PATH</envar> 63 65 time and again to find the same executable. However, the new tools should 64 be used as soon as they are installed. By switching off the hash function,65 the shell will always search the <envar>PATH</envar> whena program is to66 be used as soon as they are installed. Switching off the hash function forces 67 the shell to search the <envar>PATH</envar> whenever a program is to 66 68 be run. As such, the shell will find the newly compiled tools in 67 69 <filename class="directory">$LFS/tools/bin</filename> as soon as they are … … 119 121 <term><parameter>PATH=/usr/bin</parameter></term> 120 122 <listitem> 121 <para>Many modern linux distributions have merged <filename123 <para>Many modern Linux distributions have merged <filename 122 124 class="directory">/bin</filename> and <filename 123 125 class="directory">/usr/bin</filename>. When this is the case, the standard 124 <envar>PATH</envar> variable needs just tobe set to <filename126 <envar>PATH</envar> variable should be set to <filename 125 127 class="directory">/usr/bin/</filename> for the <xref 126 128 linkend="chapter-temporary-tools"/> environment. When this is not the … … 145 147 of <xref linkend="chapter-cross-tools"/> is picked up by the shell 146 148 immediately after its installation. This, combined with turning off hashing, 147 limits the risk that the compiler from the host beused instead of the149 limits the risk that the compiler from the host is used instead of the 148 150 cross-compiler.</para> 149 151 </listitem> … … 199 201 200 202 <para>Finally, to have the environment fully prepared for building the 201 temporary tools, source the just-created user profile:</para> 203 temporary tools, force the <command>bash</command> shell to read 204 the new user profile:</para> 202 205 203 206 <screen><userinput>source ~/.bash_profile</userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.