1 | <sect1 id="ch05-settingenviron">
|
---|
2 | <title>Setting up the environment</title>
|
---|
3 | <?dbhtml filename="settingenviron.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 | LDFLAGS="-s"
|
---|
14 | PATH=/stage1/bin:$PATH
|
---|
15 | export LFS LC_ALL LDFLAGS PATH
|
---|
16 | EOF
|
---|
17 | source ~/.bash_profile</userinput></screen></para>
|
---|
18 |
|
---|
19 | <para><userinput>set +h</userinput> turns off Bash's hash function. Hash
|
---|
20 | normally is a useful feature where Bash uses a hash table to remember the
|
---|
21 | full pathnames of executable files to avoid multiple `PATH' searches.
|
---|
22 | However, we'd like the new tools to become available as soon as they are
|
---|
23 | installed. By switching off the hash function, our "interactive" commands
|
---|
24 | (make, patch, sed, cp and so forth) will always use the newest available
|
---|
25 | during the build process.</para>
|
---|
26 |
|
---|
27 | <para>This profile sets the umask to 022, so newly created files and
|
---|
28 | directories will have the correct permissions. To be more specific, only
|
---|
29 | the file owner will have write permission to new files and directories.
|
---|
30 | Other users of the system will be have read permission, and executable
|
---|
31 | permission to directories. It is advisable to keep this setting throughout
|
---|
32 | your LFS installation.</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 "C" or "POSIX" 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" ("C" is an alias for "POSIX") we ensure that
|
---|
43 | everything will work as expected in the chroot environment.</para>
|
---|
44 |
|
---|
45 | <para>LDFLAGS is a variable we set in order to prevent debugging symbols from
|
---|
46 | being compiled into our static packages. By omitting these symbols during
|
---|
47 | the linking stage of compilation, we save hard drive space and decrease our
|
---|
48 | build time.</para>
|
---|
49 |
|
---|
50 | <para>We are now prepared to begin building the temporary tools which will
|
---|
51 | support us in later chapters.</para>
|
---|
52 |
|
---|
53 | </sect1>
|
---|
54 |
|
---|