[7152faa] | 1 | <?xml version="1.0" encoding="UTF-8"?>
|
---|
[b06ca36] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
[673b0d8] | 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
[6a3b6af] | 7 |
|
---|
[afcfd74] | 8 | <sect1 id="ch-preps-settingenviron">
|
---|
[6a3b6af] | 9 | <?dbhtml filename="settingenvironment.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Setting Up the Environment</title>
|
---|
[673b0d8] | 12 |
|
---|
[6a3b6af] | 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>
|
---|
[81fd230] | 17 |
|
---|
[05616e2] | 18 | <screen><userinput>cat > ~/.bash_profile << "EOF"
|
---|
[d72e04a] | 19 | <literal>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</literal>
|
---|
[55851d6] | 20 | EOF</userinput></screen>
|
---|
[673b0d8] | 21 |
|
---|
[4e26453] | 22 | <para>When logged on as user <systemitem class="username">lfs</systemitem>,
|
---|
| 23 | or when switched to the &lfs-user; user using an <command>su</command> command
|
---|
| 24 | with the <quote><parameter>-</parameter></quote> option,
|
---|
[aa9ade1] | 25 | the initial shell is a <emphasis>login</emphasis> shell which reads
|
---|
[6a3b6af] | 26 | the <filename>/etc/profile</filename> of the host (probably containing some
|
---|
| 27 | settings and environment variables) and then <filename>.bash_profile</filename>.
|
---|
| 28 | The <command>exec env -i.../bin/bash</command> command in the
|
---|
| 29 | <filename>.bash_profile</filename> file replaces the running shell with a new
|
---|
| 30 | one with a completely empty environment, except for the <envar>HOME</envar>,
|
---|
| 31 | <envar>TERM</envar>, and <envar>PS1</envar> variables. This ensures that no
|
---|
| 32 | unwanted and potentially hazardous environment variables from the host system
|
---|
[4e26453] | 33 | leak into the build environment.</para>
|
---|
[81fd230] | 34 |
|
---|
[6a3b6af] | 35 | <para>The new instance of the shell is a <emphasis>non-login</emphasis>
|
---|
[ec7b0466] | 36 | shell, which does not read, and execute, the contents of the <filename>/etc/profile</filename> or
|
---|
[df43be1] | 37 | <filename>.bash_profile</filename> files, but rather reads, and executes, the
|
---|
[6a3b6af] | 38 | <filename>.bashrc</filename> file instead. Create the
|
---|
| 39 | <filename>.bashrc</filename> file now:</para>
|
---|
[81fd230] | 40 |
|
---|
[05616e2] | 41 | <screen><userinput>cat > ~/.bashrc << "EOF"
|
---|
[d72e04a] | 42 | <literal>set +h
|
---|
[673b0d8] | 43 | umask 022
|
---|
| 44 | LFS=/mnt/lfs
|
---|
| 45 | LC_ALL=POSIX
|
---|
[0bd1c05] | 46 | LFS_TGT=<replaceable>x86_64</replaceable>-lfs-linux-gnu
|
---|
[b454589] | 47 | PATH=/usr/bin
|
---|
[a97aa3d] | 48 | if [ ! -L /bin ]; then PATH=/bin:$PATH; fi
|
---|
[b454589] | 49 | PATH=$LFS/tools/bin:$PATH
|
---|
[df77b24] | 50 | CONFIG_SITE=$LFS/usr/share/config.site
|
---|
| 51 | export LFS LC_ALL LFS_TGT PATH CONFIG_SITE</literal>
|
---|
[55851d6] | 52 | EOF</userinput></screen>
|
---|
[673b0d8] | 53 |
|
---|
[df43be1] | 54 | <variablelist>
|
---|
[ee714d3] | 55 | <title>The meaning of the settings in <filename>.bashrc</filename></title>
|
---|
[df43be1] | 56 |
|
---|
| 57 | <varlistentry>
|
---|
| 58 | <term><parameter>set +h</parameter></term>
|
---|
| 59 | <listitem>
|
---|
[6a3b6af] | 60 | <para>The <command>set +h</command> command turns off
|
---|
| 61 | <command>bash</command>'s hash function. Hashing is ordinarily a useful
|
---|
| 62 | feature—<command>bash</command> uses a hash table to remember the
|
---|
[ec7b0466] | 63 | full path to executable files to avoid searching the <envar>PATH</envar>
|
---|
[6a3b6af] | 64 | time and again to find the same executable. However, the new tools should
|
---|
[ec7b0466] | 65 | be used as soon as they are installed. Switching off the hash function forces
|
---|
| 66 | the shell to search the <envar>PATH</envar> whenever a program is to
|
---|
[6a3b6af] | 67 | be run. As such, the shell will find the newly compiled tools in
|
---|
[490dc153] | 68 | <filename class="directory">$LFS/tools/bin</filename> as soon as they are
|
---|
| 69 | available without remembering a previous version of the same program
|
---|
| 70 | provided by the host distro, in
|
---|
| 71 | <filename class='directory'>/usr/bin</filename> or
|
---|
| 72 | <filename class='directory'>/bin</filename>.</para>
|
---|
[df43be1] | 73 | </listitem>
|
---|
| 74 | </varlistentry>
|
---|
[81fd230] | 75 |
|
---|
[df43be1] | 76 | <varlistentry>
|
---|
| 77 | <term><parameter>umask 022</parameter></term>
|
---|
| 78 | <listitem>
|
---|
[6a3b6af] | 79 | <para>Setting the user file-creation mask (umask) to 022 ensures that newly
|
---|
| 80 | created files and directories are only writable by their owner, but are
|
---|
| 81 | readable and executable by anyone (assuming default modes are used by the
|
---|
[ea93c11] | 82 | <ulink role='man' url='&man;open.2'>open(2)</ulink> system call, new files
|
---|
| 83 | will end up with permission mode 644 and directories with mode 755).</para>
|
---|
[df43be1] | 84 | </listitem>
|
---|
| 85 | </varlistentry>
|
---|
[81fd230] | 86 |
|
---|
[df43be1] | 87 | <varlistentry>
|
---|
| 88 | <term><parameter>LFS=/mnt/lfs</parameter></term>
|
---|
| 89 | <listitem>
|
---|
[6a3b6af] | 90 | <para>The <envar>LFS</envar> variable should be set to the chosen mount
|
---|
| 91 | point.</para>
|
---|
[df43be1] | 92 | </listitem>
|
---|
| 93 | </varlistentry>
|
---|
[81fd230] | 94 |
|
---|
[df43be1] | 95 | <varlistentry>
|
---|
| 96 | <term><parameter>LC_ALL=POSIX</parameter></term>
|
---|
| 97 | <listitem>
|
---|
[6a3b6af] | 98 | <para>The <envar>LC_ALL</envar> variable controls the localization of certain
|
---|
| 99 | programs, making their messages follow the conventions of a specified country.
|
---|
[448e226] | 100 | Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> or <quote>C</quote>
|
---|
| 101 | (the two are equivalent) ensures that everything will work as expected in
|
---|
[4e26453] | 102 | the cross-compilation environment.</para>
|
---|
[df43be1] | 103 | </listitem>
|
---|
| 104 | </varlistentry>
|
---|
[81fd230] | 105 |
|
---|
[df43be1] | 106 | <varlistentry>
|
---|
[0bd1c05] | 107 | <term><parameter>LFS_TGT=<replaceable>x86_64</replaceable>-lfs-linux-gnu</parameter></term>
|
---|
[df43be1] | 108 | <listitem>
|
---|
[4e82d47] | 109 | <para>The <envar>LFS_TGT</envar> variable sets a non-default, but compatible machine
|
---|
[4e26453] | 110 | description for use when building our cross-compiler and linker and when
|
---|
| 111 | cross-compiling our temporary toolchain. More information is provided by
|
---|
[0bd1c05] | 112 | <xref linkend="ch-tools-toolchaintechnotes" role=""/>.
|
---|
| 113 | If you are not building for 64-bit x86, replace
|
---|
| 114 | <replaceable>x86_64</replaceable> with some value suitable for your target
|
---|
| 115 | machine, for example <literal>i686</literal> for 32-bit x86.</para>
|
---|
[df43be1] | 116 | </listitem>
|
---|
| 117 | </varlistentry>
|
---|
[4e82d47] | 118 |
|
---|
[df43be1] | 119 | <varlistentry>
|
---|
[b454589] | 120 | <term><parameter>PATH=/usr/bin</parameter></term>
|
---|
| 121 | <listitem>
|
---|
[ec7b0466] | 122 | <para>Many modern Linux distributions have merged <filename
|
---|
[b454589] | 123 | class="directory">/bin</filename> and <filename
|
---|
| 124 | class="directory">/usr/bin</filename>. When this is the case, the standard
|
---|
[ec7b0466] | 125 | <envar>PATH</envar> variable should be set to <filename
|
---|
[b454589] | 126 | class="directory">/usr/bin/</filename> for the <xref
|
---|
| 127 | linkend="chapter-temporary-tools"/> environment. When this is not the
|
---|
| 128 | case, the following line adds <filename class="directory">/bin</filename>
|
---|
| 129 | to the path.</para>
|
---|
| 130 | </listitem>
|
---|
| 131 | </varlistentry>
|
---|
| 132 |
|
---|
| 133 | <varlistentry>
|
---|
[a97aa3d] | 134 | <term><parameter>if [ ! -L /bin ]; then PATH=/bin:$PATH; fi</parameter></term>
|
---|
[b454589] | 135 | <listitem>
|
---|
| 136 | <para>If <filename class="directory">/bin</filename> is not a symbolic
|
---|
[4e26453] | 137 | link, it must be added to the <envar>PATH</envar> variable.</para>
|
---|
[b454589] | 138 | </listitem>
|
---|
| 139 | </varlistentry>
|
---|
| 140 |
|
---|
| 141 | <varlistentry>
|
---|
| 142 | <term><parameter>PATH=$LFS/tools/bin:$PATH</parameter></term>
|
---|
[df43be1] | 143 | <listitem>
|
---|
[efcb393] | 144 | <para>By putting <filename class="directory">$LFS/tools/bin</filename> ahead of the
|
---|
[b454589] | 145 | standard <envar>PATH</envar>, the cross-compiler installed at the beginning
|
---|
[ee714d3] | 146 | of <xref linkend="chapter-cross-tools"/> is picked up by the shell
|
---|
[b454589] | 147 | immediately after its installation. This, combined with turning off hashing,
|
---|
[ec7b0466] | 148 | limits the risk that the compiler from the host is used instead of the
|
---|
[b454589] | 149 | cross-compiler.</para>
|
---|
[df43be1] | 150 | </listitem>
|
---|
| 151 | </varlistentry>
|
---|
| 152 |
|
---|
| 153 | <varlistentry>
|
---|
[df77b24] | 154 | <term><parameter>CONFIG_SITE=$LFS/usr/share/config.site</parameter></term>
|
---|
| 155 | <listitem>
|
---|
| 156 | <para>In <xref linkend="chapter-cross-tools"/> and
|
---|
| 157 | <xref linkend="chapter-temporary-tools"/>, if this variable is not set,
|
---|
| 158 | <command>configure</command> scripts
|
---|
[a2d41cf2] | 159 | may attempt to load configuration items specific to some distributions from
|
---|
| 160 | <filename>/usr/share/config.site</filename> on the host system. Override
|
---|
| 161 | it to prevent potential contamination from the host.</para>
|
---|
[df77b24] | 162 | </listitem>
|
---|
| 163 | </varlistentry>
|
---|
| 164 |
|
---|
| 165 | <varlistentry>
|
---|
| 166 | <term><parameter>export ...</parameter></term>
|
---|
[df43be1] | 167 | <listitem>
|
---|
[4e26453] | 168 | <para>While the preceding commands have set some variables, in order
|
---|
[ee714d3] | 169 | to make them visible within any sub-shells, we export them.</para>
|
---|
[df43be1] | 170 | </listitem>
|
---|
| 171 | </varlistentry>
|
---|
| 172 |
|
---|
| 173 | </variablelist>
|
---|
[81fd230] | 174 |
|
---|
[686c88b] | 175 | <important>
|
---|
| 176 |
|
---|
[4e26453] | 177 | <para>Several commercial distributions add an undocumented instantiation
|
---|
[686c88b] | 178 | of <filename>/etc/bash.bashrc</filename> to the initialization of
|
---|
[3a38c46] | 179 | <command>bash</command>. This file has the potential to modify the
|
---|
| 180 | <systemitem class="username">lfs</systemitem>
|
---|
[dbb9122] | 181 | user's environment in ways that can affect the building of critical LFS
|
---|
[3a38c46] | 182 | packages. To make sure the <systemitem class="username">lfs</systemitem>
|
---|
[c0c616a] | 183 | user's environment is clean, check for the
|
---|
[686c88b] | 184 | presence of <filename>/etc/bash.bashrc</filename> and, if present, move it
|
---|
[3a38c46] | 185 | out of the way. As the <systemitem class="username">root</systemitem>
|
---|
| 186 | user, run:</para>
|
---|
[686c88b] | 187 |
|
---|
[707c4d3] | 188 | <screen role="nodump"><userinput>[ ! -e /etc/bash.bashrc ] || mv -v /etc/bash.bashrc /etc/bash.bashrc.NOUSE</userinput></screen>
|
---|
[686c88b] | 189 |
|
---|
[4e26453] | 190 | <para>When the <systemitem class="username">lfs</systemitem>
|
---|
| 191 | user is no longer needed (at the beginning of <xref
|
---|
| 192 | linkend="chapter-chroot-temporary-tools"/>), you may safely restore
|
---|
[c37e846] | 193 | <filename>/etc/bash.bashrc</filename> (if desired).</para>
|
---|
[3a38c46] | 194 |
|
---|
| 195 | <para>Note that the LFS Bash package we will build in
|
---|
| 196 | <xref linkend="ch-system-bash"/> is not configured to load or execute
|
---|
| 197 | <filename>/etc/bash.bashrc</filename>, so this file is useless on a
|
---|
| 198 | completed LFS system.</para>
|
---|
[686c88b] | 199 | </important>
|
---|
| 200 |
|
---|
[a0a803c] | 201 | <para>
|
---|
| 202 | For many modern systems with multiple processors (or cores) the
|
---|
| 203 | compilation time for a package can be reduced by performing a "parallel
|
---|
| 204 | make" by telling the make program how many processors are available via
|
---|
| 205 | a command line option or an environment variable. For instance, an Intel
|
---|
| 206 | Core i9-13900K processor has 8 P (performance) cores and
|
---|
| 207 | 16 E (efficiency) cores, and a P core can simultaneously run two threads
|
---|
| 208 | so each P core are modeled as two logical cores by the Linux kernel.
|
---|
| 209 | As the result there are 32 logical cores in total. One obvious way to
|
---|
| 210 | use all these logical cores is allowing <command>make</command> to spawn
|
---|
| 211 | up to 32 build jobs. This can be done by passing the
|
---|
| 212 | <parameter>-j32</parameter> option to <command>make</command>:
|
---|
| 213 | </para>
|
---|
| 214 |
|
---|
| 215 | <screen role='nodump'><userinput>make -j32</userinput></screen>
|
---|
| 216 |
|
---|
| 217 | <para>
|
---|
| 218 | Or set the <envar>MAKEFLAGS</envar> environment variable and its
|
---|
| 219 | content will be automatically used by <command>make</command> as
|
---|
| 220 | command line options:
|
---|
| 221 | </para>
|
---|
| 222 |
|
---|
| 223 | <screen role='nodump'><userinput>export MAKEFLAGS=-j32</userinput></screen>
|
---|
| 224 |
|
---|
| 225 | <important>
|
---|
| 226 | <para>
|
---|
| 227 | Never pass a <parameter>-j</parameter> option without a number to
|
---|
| 228 | <command>make</command> or set such an option in
|
---|
| 229 | <envar>MAKEFLAGS</envar>. Doing so will allow <command>make</command>
|
---|
[6554500] | 230 | to spawn infinite build jobs and cause system stability problems.
|
---|
[a0a803c] | 231 | </para>
|
---|
| 232 | </important>
|
---|
| 233 |
|
---|
| 234 | <para>
|
---|
| 235 | To use all logical cores available for building packages in
|
---|
| 236 | <xref linkend='chapter-cross-tools'/> and
|
---|
| 237 | <xref linkend='chapter-temporary-tools'/>, set <envar>MAKEFLAGS</envar>
|
---|
| 238 | now in <filename>.bashrc</filename>:
|
---|
| 239 | </para>
|
---|
| 240 |
|
---|
| 241 | <screen><userinput>cat >> ~/.bashrc << "EOF"
|
---|
| 242 | <literal>export MAKEFLAGS=-j<replaceable>$(nproc)</replaceable></literal>
|
---|
| 243 | EOF</userinput></screen>
|
---|
| 244 |
|
---|
| 245 | <para>
|
---|
| 246 | Replace <replaceable>$(nproc)</replaceable> with the number of logical
|
---|
| 247 | cores you want to use if you don't want to use all the logical cores.
|
---|
| 248 | </para>
|
---|
| 249 |
|
---|
[4e26453] | 250 | <para>Finally, to ensure the environment is fully prepared for building the
|
---|
[ec7b0466] | 251 | temporary tools, force the <command>bash</command> shell to read
|
---|
| 252 | the new user profile:</para>
|
---|
[81fd230] | 253 |
|
---|
[673b0d8] | 254 | <screen><userinput>source ~/.bash_profile</userinput></screen>
|
---|
| 255 |
|
---|
| 256 | </sect1>
|
---|