1 | <sect1 id="ch05-settingenviron">
|
---|
2 | <title>Setting up the environment</title>
|
---|
3 | <?dbhtml filename="settingenvironment.html" dir="chapter05"?>
|
---|
4 |
|
---|
5 | <para>While logged in as user <emphasis>lfs</emphasis>, issue the
|
---|
6 | following commands to set up a good work environment:</para>
|
---|
7 |
|
---|
8 | <para><screen><userinput>cat > ~/.bash_profile << "EOF"
|
---|
9 | set +h
|
---|
10 | umask 022
|
---|
11 | LFS=/mnt/lfs
|
---|
12 | LC_ALL=POSIX
|
---|
13 | PATH=/stage1/bin:$PATH
|
---|
14 | export LFS LC_ALL PATH
|
---|
15 | EOF
|
---|
16 |
|
---|
17 | source ~/.bash_profile</userinput></screen></para>
|
---|
18 |
|
---|
19 | <para>The <userinput>set +h</userinput> command turns off
|
---|
20 | <userinput>bash</userinput>'s hash function. Normally hashing is a useful
|
---|
21 | feature: <userinput>bash</userinput> uses a hash table to remember the
|
---|
22 | full pathnames of executable files to avoid searching the PATH time and time
|
---|
23 | again to find the same executable. However, we'd like the new tools to be
|
---|
24 | used as soon as they are installed. By switching off the hash function, our
|
---|
25 | "interactive" commands (<userinput>make</userinput>,
|
---|
26 | <userinput>patch</userinput>, <userinput>sed</userinput>,
|
---|
27 | <userinput>cp</userinput> and so forth) will always use
|
---|
28 | the newest available version during the build process.</para>
|
---|
29 |
|
---|
30 | <para>Setting the user file-creation mask to 022 ensures that newly created
|
---|
31 | files and directories are only writable for their owner, but readable and
|
---|
32 | executable for anyone.</para>
|
---|
33 |
|
---|
34 | <para>The LFS variable should of course be set to the mount point you
|
---|
35 | chose.</para>
|
---|
36 |
|
---|
37 | <para>The LC_ALL variable controls the localization of certain programs,
|
---|
38 | making their messages follow the conventions of a specified country. If your
|
---|
39 | host system uses a version of <emphasis>glibc</emphasis> older than 2.2.4,
|
---|
40 | having LC_ALL set to something other than "POSIX" or "C" during this chapter
|
---|
41 | may cause trouble if you exit the chroot environment and wish to return later.
|
---|
42 | By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that
|
---|
43 | everything will work as expected in the chroot environment.</para>
|
---|
44 |
|
---|
45 | <para>We prepend <filename>/stage1/bin</filename> to the standard PATH so
|
---|
46 | that, as we move along through this chapter, the tools we build will get used
|
---|
47 | during the rest of the building process.</para>
|
---|
48 |
|
---|
49 | <para>Now, after sourcing the just-created profile, we're all set to begin
|
---|
50 | building the temporary tools that will support us in later chapters.</para>
|
---|
51 |
|
---|
52 | </sect1>
|
---|
53 |
|
---|