[1fa2099] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
| 7 |
|
---|
[ede49cd] | 8 | <sect1 id="ch-preps-settingenviron">
|
---|
[1fa2099] | 9 | <?dbhtml filename="settingenvironment.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Setting Up the Environment</title>
|
---|
| 12 |
|
---|
| 13 | <para>Set up a good working environment by creating two new startup files
|
---|
| 14 | for the <command>bash</command> shell. While logged in as user
|
---|
| 15 | <systemitem class="username">lfs</systemitem>, issue the following command
|
---|
| 16 | to create a new <filename>.bash_profile</filename>:</para>
|
---|
| 17 |
|
---|
| 18 | <screen><userinput>cat > ~/.bash_profile << "EOF"
|
---|
| 19 | <literal>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</literal>
|
---|
| 20 | EOF</userinput></screen>
|
---|
| 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
|
---|
| 24 | the <filename>/etc/profile</filename> of the host (probably containing some
|
---|
| 25 | settings and environment variables) and then <filename>.bash_profile</filename>.
|
---|
| 26 | The <command>exec env -i.../bin/bash</command> command in the
|
---|
| 27 | <filename>.bash_profile</filename> file replaces the running shell with a new
|
---|
| 28 | one with a completely empty environment, except for the <envar>HOME</envar>,
|
---|
| 29 | <envar>TERM</envar>, and <envar>PS1</envar> variables. This ensures that no
|
---|
| 30 | unwanted and potentially hazardous environment variables from the host system
|
---|
| 31 | leak into the build environment. The technique used here achieves the goal of
|
---|
| 32 | ensuring a clean environment.</para>
|
---|
| 33 |
|
---|
| 34 | <para>The new instance of the shell is a <emphasis>non-login</emphasis>
|
---|
[88ec930] | 35 | shell, which does not read, and execute, the conten of <filename>/etc/profile</filename> or
|
---|
| 36 | <filename>.bash_profile</filename> files, but rather reads, and executes, the
|
---|
[1fa2099] | 37 | <filename>.bashrc</filename> file instead. Create the
|
---|
| 38 | <filename>.bashrc</filename> file now:</para>
|
---|
| 39 |
|
---|
[8eb3fe4] | 40 | <screen arch="default"><userinput>cat > ~/.bashrc << "EOF"
|
---|
[1fa2099] | 41 | <literal>set +h
|
---|
| 42 | umask 022
|
---|
| 43 | LFS=/mnt/lfs
|
---|
| 44 | LC_ALL=POSIX
|
---|
| 45 | LFS_TGT=$(uname -m)-lfs-linux-gnu
|
---|
| 46 | PATH=/tools/bin:/bin:/usr/bin
|
---|
| 47 | export LFS LC_ALL LFS_TGT PATH</literal>
|
---|
[8eb3fe4] | 48 | EOF</userinput></screen>
|
---|
[ee1a413] | 49 | <screen arch="ml_32,ml_x32,ml_all"><userinput>cat > ~/.bashrc << "EOF"
|
---|
[8eb3fe4] | 50 | <literal>set +h
|
---|
| 51 | umask 022
|
---|
| 52 | LFS=/mnt/lfs
|
---|
| 53 | LC_ALL=POSIX
|
---|
| 54 | LFS_TGT=x86_64-lfs-linux-gnu
|
---|
| 55 | LFS_TGT32=i686-lfs-linux-gnu
|
---|
| 56 | LFS_TGTX32=x86_64-lfs-linux-gnux32
|
---|
| 57 | PATH=/tools/bin:/bin:/usr/bin
|
---|
| 58 | export LFS LC_ALL LFS_TGT LFS_TGT32 LFS_TGTX32 PATH</literal>
|
---|
[1fa2099] | 59 | EOF</userinput></screen>
|
---|
| 60 |
|
---|
[88ec930] | 61 | <variablelist>
|
---|
| 62 | <title>The meaning of the command line options in <filename>.bashrc</filename></title>
|
---|
| 63 |
|
---|
| 64 | <varlistentry>
|
---|
| 65 | <term><parameter>set +h</parameter></term>
|
---|
| 66 | <listitem>
|
---|
[1fa2099] | 67 | <para>The <command>set +h</command> command turns off
|
---|
| 68 | <command>bash</command>'s hash function. Hashing is ordinarily a useful
|
---|
| 69 | feature—<command>bash</command> uses a hash table to remember the
|
---|
| 70 | full path of executable files to avoid searching the <envar>PATH</envar>
|
---|
| 71 | time and again to find the same executable. However, the new tools should
|
---|
| 72 | be used as soon as they are installed. By switching off the hash function,
|
---|
| 73 | the shell will always search the <envar>PATH</envar> when a program is to
|
---|
| 74 | be run. As such, the shell will find the newly compiled tools in
|
---|
| 75 | <filename class="directory">$LFS/tools</filename> as soon as they are
|
---|
| 76 | available without remembering a previous version of the same program in a
|
---|
| 77 | different location.</para>
|
---|
[88ec930] | 78 | </listitem>
|
---|
| 79 | </varlistentry>
|
---|
[1fa2099] | 80 |
|
---|
[88ec930] | 81 | <varlistentry>
|
---|
| 82 | <term><parameter>umask 022</parameter></term>
|
---|
| 83 | <listitem>
|
---|
[1fa2099] | 84 | <para>Setting the user file-creation mask (umask) to 022 ensures that newly
|
---|
| 85 | created files and directories are only writable by their owner, but are
|
---|
| 86 | readable and executable by anyone (assuming default modes are used by the
|
---|
| 87 | <function>open(2)</function> system call, new files will end up with permission
|
---|
| 88 | mode 644 and directories with mode 755).</para>
|
---|
[88ec930] | 89 | </listitem>
|
---|
| 90 | </varlistentry>
|
---|
[1fa2099] | 91 |
|
---|
[88ec930] | 92 | <varlistentry>
|
---|
| 93 | <term><parameter>LFS=/mnt/lfs</parameter></term>
|
---|
| 94 | <listitem>
|
---|
[1fa2099] | 95 | <para>The <envar>LFS</envar> variable should be set to the chosen mount
|
---|
| 96 | point.</para>
|
---|
[88ec930] | 97 | </listitem>
|
---|
| 98 | </varlistentry>
|
---|
[1fa2099] | 99 |
|
---|
[88ec930] | 100 | <varlistentry>
|
---|
| 101 | <term><parameter>LC_ALL=POSIX</parameter></term>
|
---|
| 102 | <listitem>
|
---|
[1fa2099] | 103 | <para>The <envar>LC_ALL</envar> variable controls the localization of certain
|
---|
| 104 | programs, making their messages follow the conventions of a specified country.
|
---|
| 105 | Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> or <quote>C</quote>
|
---|
| 106 | (the two are equivalent) ensures that everything will work as expected in
|
---|
| 107 | the chroot environment.</para>
|
---|
[88ec930] | 108 | </listitem>
|
---|
| 109 | </varlistentry>
|
---|
[1fa2099] | 110 |
|
---|
[88ec930] | 111 | <varlistentry>
|
---|
| 112 | <term><parameter>LFS_TGT=(uname -m)-lfs-linux-gnu</parameter></term>
|
---|
| 113 | <listitem>
|
---|
[1fa2099] | 114 | <para>The <envar>LFS_TGT</envar> variable sets a non-default, but compatible machine
|
---|
| 115 | description for use when building our cross compiler and linker and when cross
|
---|
| 116 | compiling our temporary toolchain. More information is contained in
|
---|
| 117 | <xref linkend="ch-tools-toolchaintechnotes" role=""/>.</para>
|
---|
[88ec930] | 118 | </listitem>
|
---|
| 119 | </varlistentry>
|
---|
[1fa2099] | 120 |
|
---|
[88ec930] | 121 | <varlistentry>
|
---|
| 122 | <term><parameter>PATH=/tools/bin:/bin:/usr/bin</parameter></term>
|
---|
| 123 | <listitem>
|
---|
[1fa2099] | 124 | <para>By putting <filename class="directory">/tools/bin</filename> ahead of the
|
---|
| 125 | standard <envar>PATH</envar>, all the programs installed in <xref
|
---|
| 126 | linkend="chapter-temporary-tools"/> are picked up by the shell immediately after
|
---|
| 127 | their installation. This, combined with turning off hashing, limits the risk
|
---|
| 128 | that old programs are used from the host when the same programs are available in
|
---|
[88ec930] | 129 | the Chapter 5 environment.</para>
|
---|
| 130 | </listitem>
|
---|
| 131 | </varlistentry>
|
---|
| 132 |
|
---|
| 133 | <varlistentry>
|
---|
| 134 | <term><parameter>export LFS LC_ALL LFS_TGT PATH</parameter></term>
|
---|
| 135 | <listitem>
|
---|
| 136 | <para>While the above commands have set some variables, in order
|
---|
| 137 | to make them visible within any sub-shells, we export them</para>
|
---|
| 138 | </listitem>
|
---|
| 139 | </varlistentry>
|
---|
| 140 |
|
---|
| 141 | </variablelist>
|
---|
[1fa2099] | 142 |
|
---|
| 143 | <para>Finally, to have the environment fully prepared for building the
|
---|
| 144 | temporary tools, source the just-created user profile:</para>
|
---|
| 145 |
|
---|
| 146 | <screen><userinput>source ~/.bash_profile</userinput></screen>
|
---|
| 147 |
|
---|
| 148 | </sect1>
|
---|