Changeset a9e0b22
- Timestamp:
- 09/05/2004 09:58:29 AM (20 years ago)
- Branches:
- 6.0
- Children:
- e097438
- Parents:
- 3a49def
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/mounting.xml
r3a49def ra9e0b22 15 15 to you.</para> 16 16 17 <para>Choose a mount point and assign it to the LFS environment18 variable by running:</para>17 <para>Choose a mount point and assign it to the <envar>LFS</envar> 18 environment variable by running:</para> 19 19 20 20 <screen><userinput>export LFS=/mnt/lfs</userinput></screen> -
chapter04/aboutlfs.xml
r3a49def ra9e0b22 8 8 <?dbhtml filename="aboutlfs.html"?> 9 9 10 <para>Throughout this book, the environment variable LFS will be used11 several times. It is paramount that this variable is always defined.10 <para>Throughout this book, the environment variable <envar>LFS</envar> will 11 be used several times. It is paramount that this variable is always defined. 12 12 It should be set to the mount point chosen for the LFS partition. 13 Check that the LFSvariable is set up properly with:</para>13 Check that the <envar>LFS</envar> variable is set up properly with:</para> 14 14 15 15 <screen><userinput>echo $LFS</userinput></screen> … … 28 28 processes the command line.</para> 29 29 30 <para>Do not forget to check that < quote>$LFS</quote> is set whenever30 <para>Do not forget to check that <envar>$LFS</envar> is set whenever 31 31 you leave and reenter the current working environment (as when doing a 32 32 <quote>su</quote> to <emphasis>root</emphasis> or another user).</para> -
chapter04/settingenviron.xml
r3a49def ra9e0b22 25 25 <filename>.bash_profile</filename> file replaces the running shell 26 26 with a new one with a completely empty environment, except for the 27 <e mphasis>HOME</emphasis>, <emphasis>TERM</emphasis>, and28 <e mphasis>PS1</emphasis> variables. This ensures that no unwanted and27 <envar>HOME</envar>, <envar>TERM</envar>, and 28 <envar>PS1</envar> variables. This ensures that no unwanted and 29 29 potentially hazardous environment variables from the host system leak 30 30 into the build environment. The technique used here achieves the goal … … 49 49 <command>bash</command>'s hash function. Hashing is ordinarily a useful 50 50 feature—<command>bash</command> uses a hash table to remember the 51 full pathnames of executable files to avoid searching the PATHtime51 full pathnames of executable files to avoid searching the <envar>PATH</envar> time 52 52 and again to find the same executable. However, the new tools 53 53 should be used as soon as they are installed. By switching off the 54 hash function, the shell will always search the PATHwhen a program is54 hash function, the shell will always search the <envar>PATH</envar> when a program is 55 55 to be run. As such, the shell will find the newly compiled 56 56 tools in <filename class="directory">$LFS/tools</filename> as soon as … … 64 64 644 and directories with mode 755).</para> 65 65 66 <para>The <e mphasis>LFS</emphasis> variable should be set to the66 <para>The <envar>LFS</envar> variable should be set to the 67 67 chosen mount point.</para> 68 68 69 <para>The <e mphasis>LC_ALL</emphasis> variable controls the69 <para>The <envar>LC_ALL</envar> variable controls the 70 70 localization of certain programs, making their messages follow the 71 71 conventions of a specified country. If the host system uses a version 72 of Glibc older than 2.2.4, having LC_ALLset to something other than72 of Glibc older than 2.2.4, having <envar>LC_ALL</envar> set to something other than 73 73 <quote>POSIX</quote> or <quote>C</quote> (during this chapter) may 74 74 cause issues if you exit the chroot environment and wish to return 75 later. Setting <e mphasis>LC_ALL</emphasis> to <quote>POSIX</quote>75 later. Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> 76 76 or <quote>C</quote> (the two are equivalent) ensures that 77 77 everything will work as expected in the chroot environment.</para> 78 78 79 79 <para>By putting <filename class="directory">/tools/bin</filename> 80 ahead of the standard PATH, all the programs installed in <xref80 ahead of the standard <envar>PATH</envar>, all the programs installed in <xref 81 81 linkend="chapter-temporary-tools"/> are picked up by the shell 82 82 immediately after their installation. This, combined with turning off
Note:
See TracChangeset
for help on using the changeset viewer.