1 | <chapter id="chapter05" xreflabel="Chapter 5">
|
---|
2 | <title>Constructing a temporary system</title>
|
---|
3 | <?dbhtml filename="chapter05.html" dir="chapter05"?>
|
---|
4 |
|
---|
5 |
|
---|
6 | <sect1 id="ch-tools-introduction">
|
---|
7 | <title>Introduction</title>
|
---|
8 | <?dbhtml filename="introduction.html" dir="chapter05"?>
|
---|
9 |
|
---|
10 | <para>In this chapter we will compile and install a minimal
|
---|
11 | Linux system. This system will contain just enough tools to be able
|
---|
12 | to start constructing the final LFS system in the next chapter.</para>
|
---|
13 |
|
---|
14 | <para>The building of this minimal system is done in two steps: first we
|
---|
15 | build a brand-new and host-independent toolchain (compiler, assembler,
|
---|
16 | linker and libraries), and then use this to build all the other essential
|
---|
17 | tools.</para>
|
---|
18 |
|
---|
19 | <para>The files compiled in this chapter will be installed under the
|
---|
20 | <filename class="directory">$LFS/tools</filename> directory
|
---|
21 | to keep them separate from the files installed in the next chapter.
|
---|
22 | Since the packages compiled here are merely temporary, we don't want
|
---|
23 | them to pollute the soon-to-be LFS system.</para>
|
---|
24 |
|
---|
25 | <para>The build instructions assume that you are using the
|
---|
26 | <userinput>bash</userinput> shell. It is also expected that you have already
|
---|
27 | unpacked a source package (while logged in as user <emphasis>lfs</emphasis> --
|
---|
28 | explained shortly) and performed a <userinput>cd</userinput> into the source
|
---|
29 | directory of a package before issuing its build commands.</para>
|
---|
30 |
|
---|
31 | <para>Several of the packages are patched before compilation, but only when
|
---|
32 | the patch is needed to circumvent a problem. Often the patch is needed in
|
---|
33 | both this and the next chapter, but sometimes in only one of them. Therefore,
|
---|
34 | don't worry when instructions for a downloaded patch seem to be missing. When
|
---|
35 | applying a patch you'll occasionally see a warning message about
|
---|
36 | <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>. These warnings are
|
---|
37 | nothing to worry about as the patch was still successfully applied.</para>
|
---|
38 |
|
---|
39 | <para>During the installation of most packages you will
|
---|
40 | see all kinds of compiler warnings scroll by on your screen. These are
|
---|
41 | normal and can be safely ignored. They are just what they say they are:
|
---|
42 | warnings -- mostly about deprecated, but not invalid, use of the C or C++
|
---|
43 | syntax. It's just that C standards have changed rather often and some
|
---|
44 | packages still use the older standard, which is not really a problem.</para>
|
---|
45 |
|
---|
46 | <para><emphasis>Unless</emphasis> told not to, you should normally delete the
|
---|
47 | source and build directories after installing each package -- for cleanness
|
---|
48 | sake and to save space.</para>
|
---|
49 |
|
---|
50 | <para>Before continuing, make sure the LFS environment variable is set up
|
---|
51 | properly by executing the following:</para>
|
---|
52 |
|
---|
53 | <screen><userinput>echo $LFS</userinput></screen>
|
---|
54 |
|
---|
55 | <para>Make sure the output shows the path to your LFS partition's mount
|
---|
56 | point, which is <filename class="directory">/mnt/lfs</filename> if you
|
---|
57 | followed our example.</para>
|
---|
58 |
|
---|
59 | </sect1>
|
---|
60 |
|
---|
61 |
|
---|
62 | <sect1 id="ch-tools-toolchaintechnotes">
|
---|
63 | <title>Toolchain technical notes</title>
|
---|
64 | <?dbhtml filename="toolchaintechnotes.html" dir="chapter05"?>
|
---|
65 |
|
---|
66 | <para>This section attempts to explain some of the rationale and technical
|
---|
67 | details behind the overall build method. It's not essential that you understand
|
---|
68 | everything here immediately. Most of it will make sense once you have performed
|
---|
69 | an actual build. Feel free to refer back here at any time.</para>
|
---|
70 |
|
---|
71 | <para>The overall goal of <xref linkend="chapter05"/> is to provide a sane,
|
---|
72 | temporary environment that we can chroot into, and from which we can produce a
|
---|
73 | clean, trouble-free build of the target LFS system in
|
---|
74 | <xref linkend="chapter06"/>. Along the way, we attempt to divorce ourselves
|
---|
75 | from the host system as much as possible, and in so doing build a
|
---|
76 | self-contained and self-hosted toolchain. It should be noted that the
|
---|
77 | build process has been designed in such a way so as to minimize the risks for
|
---|
78 | new readers and provide maximum educational value at the same time. In other
|
---|
79 | words, more advanced techniques could be used to build the system.</para>
|
---|
80 |
|
---|
81 | <important>
|
---|
82 | <para>Before continuing, you really should be aware of the name of your working
|
---|
83 | platform, often also referred to as the <emphasis>target triplet</emphasis>. For
|
---|
84 | many folks the target triplet will probably be
|
---|
85 | <emphasis>i686-pc-linux-gnu</emphasis>. A simple way to determine your target
|
---|
86 | triplet is to run the <filename>config.guess</filename> script that comes with
|
---|
87 | the source for many packages. Unpack the Binutils sources and run the script:
|
---|
88 | <userinput>./config.guess</userinput> and note the output.</para>
|
---|
89 |
|
---|
90 | <para>You'll also need to be aware of the name of your platform's
|
---|
91 | <emphasis>dynamic linker</emphasis>, often also referred to as the
|
---|
92 | <emphasis>dynamic loader</emphasis>, not to be confused with the standard linker
|
---|
93 | <emphasis>ld</emphasis> that is part of Binutils. The dynamic linker is provided
|
---|
94 | by Glibc and has the job of finding and loading the shared libraries needed by a
|
---|
95 | program, preparing the program to run and then running it. For most folks the
|
---|
96 | name of the dynamic linker will be <emphasis>ld-linux.so.2</emphasis>. On
|
---|
97 | platforms that are less prevalent, the name might be
|
---|
98 | <emphasis>ld.so.1</emphasis> and newer 64 bit platforms might even have
|
---|
99 | something completely different. You should be able to determine the name
|
---|
100 | of your platform's dynamic linker by looking in the
|
---|
101 | <filename class="directory">/lib</filename> directory on your host system. A
|
---|
102 | surefire way is to inspect a random binary from your host system by running:
|
---|
103 | <userinput>'readelf -l <name of binary> | grep interpreter'</userinput>
|
---|
104 | and noting the output. The authoritative reference covering all platforms is in
|
---|
105 | the <filename>shlib-versions</filename> file in the root of the Glibc source
|
---|
106 | tree.</para>
|
---|
107 | </important>
|
---|
108 |
|
---|
109 | <para>Some key technical points of how the <xref linkend="chapter05"/> build
|
---|
110 | method works:</para>
|
---|
111 |
|
---|
112 | <itemizedlist>
|
---|
113 | <listitem><para>Similar in principle to cross compiling whereby tools installed
|
---|
114 | into the same prefix work in cooperation and thus utilize a little GNU
|
---|
115 | "magic".</para></listitem>
|
---|
116 |
|
---|
117 | <listitem><para>Careful manipulation of the standard linker's library search
|
---|
118 | path to ensure programs are linked only against libraries we
|
---|
119 | choose.</para></listitem>
|
---|
120 |
|
---|
121 | <listitem><para>Careful manipulation of <userinput>gcc</userinput>'s
|
---|
122 | <emphasis>specs</emphasis> file to tell the compiler which target dynamic
|
---|
123 | linker will be used.</para></listitem>
|
---|
124 | </itemizedlist>
|
---|
125 |
|
---|
126 | <para>Binutils is installed first because both GCC and Glibc perform various
|
---|
127 | feature tests on the assembler and linker during their respective runs of
|
---|
128 | <userinput>./configure</userinput> to determine which software features to enable
|
---|
129 | or disable. This is more important than one might first realize. An incorrectly
|
---|
130 | configured GCC or Glibc can result in a subtly broken toolchain where the impact
|
---|
131 | of such breakage might not show up until near the end of the build of a whole
|
---|
132 | distribution. Thankfully, a test suite failure will usually alert us before too
|
---|
133 | much time is wasted.</para>
|
---|
134 |
|
---|
135 | <para>Binutils installs its assembler and linker into two locations,
|
---|
136 | <filename class="directory">/tools/bin</filename> and
|
---|
137 | <filename class="directory">/tools/$TARGET_TRIPLET/bin</filename>. In reality,
|
---|
138 | the tools in one location are hard linked to the other. An important facet of
|
---|
139 | the linker is its library search order. Detailed information can be obtained
|
---|
140 | from <userinput>ld</userinput> by passing it the <emphasis>--verbose</emphasis>
|
---|
141 | flag. For example: <userinput>'ld --verbose | grep SEARCH'</userinput> will
|
---|
142 | show you the current search paths and their order. You can see what files are
|
---|
143 | actually linked by <userinput>ld</userinput> by compiling a dummy program and
|
---|
144 | passing the <emphasis>--verbose</emphasis> switch. For example:
|
---|
145 | <userinput>'gcc dummy.c -Wl,--verbose 2>&1 | grep succeeded'</userinput>
|
---|
146 | will show you all the files successfully opened during the link.</para>
|
---|
147 |
|
---|
148 | <para>The next package installed is GCC and during its run of
|
---|
149 | <userinput>./configure</userinput> you'll see, for example:</para>
|
---|
150 |
|
---|
151 | <blockquote><screen>checking what assembler to use... /tools/i686-pc-linux-gnu/bin/as
|
---|
152 | checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</screen></blockquote>
|
---|
153 |
|
---|
154 | <para>This is important for the reasons mentioned above. It also demonstrates
|
---|
155 | that GCC's configure script does not search the $PATH directories to find which
|
---|
156 | tools to use. However, during the actual operation of <userinput>gcc</userinput>
|
---|
157 | itself, the same search paths are not necessarily used. You can find out which
|
---|
158 | standard linker <userinput>gcc</userinput> will use by running:
|
---|
159 | <userinput>'gcc -print-prog-name=ld'</userinput>.
|
---|
160 | Detailed information can be obtained from <userinput>gcc</userinput> by passing
|
---|
161 | it the <emphasis>-v</emphasis> flag while compiling a dummy program. For
|
---|
162 | example: <userinput>'gcc -v dummy.c'</userinput> will show you detailed
|
---|
163 | information about the preprocessor, compilation and assembly stages, including
|
---|
164 | <userinput>gcc</userinput>'s include search paths and their order.</para>
|
---|
165 |
|
---|
166 | <para>The next package installed is Glibc. The most important considerations for
|
---|
167 | building Glibc are the compiler, binary tools and kernel headers. The compiler
|
---|
168 | is generally no problem as Glibc will always use the <userinput>gcc</userinput>
|
---|
169 | found in a $PATH directory. The binary tools and kernel headers can be a little
|
---|
170 | more troublesome. Therefore we take no risks and use the available configure
|
---|
171 | switches to enforce the correct selections. After the run of
|
---|
172 | <userinput>./configure</userinput> you can check the contents of the
|
---|
173 | <filename>config.make</filename> file in the
|
---|
174 | <filename class="directory">glibc-build</filename> directory for all the
|
---|
175 | important details. You'll note some interesting items like the use of
|
---|
176 | <userinput>CC="gcc -B/tools/bin/"</userinput> to control which binary tools are
|
---|
177 | used, and also the use of the <emphasis>-nostdinc</emphasis> and
|
---|
178 | <emphasis>-isystem</emphasis> flags to control the compiler's include search
|
---|
179 | path. These items help to highlight an important aspect of the Glibc package:
|
---|
180 | it is very self-sufficient in terms of its build machinery and generally does
|
---|
181 | not rely on toolchain defaults.</para>
|
---|
182 |
|
---|
183 | <para>After the Glibc installation, we make some adjustments to ensure that
|
---|
184 | searching and linking take place only within our <filename>/tools</filename>
|
---|
185 | prefix. We install an adjusted <userinput>ld</userinput>, which has a hard-wired
|
---|
186 | search path limited to <filename class="directory">/tools/lib</filename>. Then
|
---|
187 | we amend <userinput>gcc</userinput>'s specs file to point to our new dynamic
|
---|
188 | linker in <filename class="directory">/tools/lib</filename>. This last step is
|
---|
189 | <emphasis>vital</emphasis> to the whole process. As mentioned above, a
|
---|
190 | hard-wired path to a dynamic linker is embedded into every ELF shared
|
---|
191 | executable. You can inspect this by running:
|
---|
192 | <userinput>'readelf -l <name of binary> | grep interpreter'</userinput>.
|
---|
193 | By amending <userinput>gcc</userinput>'s specs file, we are ensuring that every
|
---|
194 | program compiled from here through the end of <xref linkend="chapter05"/> will
|
---|
195 | use our new dynamic linker in
|
---|
196 | <filename class="directory">/tools/lib</filename>.</para>
|
---|
197 |
|
---|
198 | <para>The need to use the new dynamic linker is also the reason why we apply the
|
---|
199 | Specs patch for the second pass of GCC. Failure to do so will result in the GCC
|
---|
200 | programs themselves having the name of the dynamic linker from the host system's
|
---|
201 | <filename class="directory">/lib</filename> directory embedded into them, which
|
---|
202 | would defeat our goal of getting away from the host.</para>
|
---|
203 |
|
---|
204 | <para>During the second pass of Binutils, we are able to utilize the
|
---|
205 | <emphasis>--with-lib-path</emphasis> configure switch to control
|
---|
206 | <userinput>ld</userinput>'s library search path. From this point onwards, the
|
---|
207 | core toolchain is self-contained and self-hosted. The remainder of the
|
---|
208 | <xref linkend="chapter05"/> packages all build against the new Glibc in
|
---|
209 | <filename class="directory">/tools</filename> and all is well.</para>
|
---|
210 |
|
---|
211 | <para>Upon entering the chroot environment in <xref linkend="chapter06"/>, the
|
---|
212 | first major package we install is Glibc, due to its self-sufficient nature that
|
---|
213 | we mentioned above. Once this Glibc is installed into
|
---|
214 | <filename class="directory">/usr</filename>, we perform a quick changeover of
|
---|
215 | the toolchain defaults, then proceed for real in building the rest of the
|
---|
216 | target <xref linkend="chapter06"/> LFS system.</para>
|
---|
217 |
|
---|
218 | <sect2>
|
---|
219 | <title>Notes on static linking</title>
|
---|
220 |
|
---|
221 | <para>Most programs have to perform, beside their specific task, many rather
|
---|
222 | common and sometimes trivial operations. These include allocating memory,
|
---|
223 | searching directories, reading and writing files, string handling, pattern
|
---|
224 | matching, arithmetic and many other tasks. Instead of obliging each program to
|
---|
225 | reinvent the wheel, the GNU system provides all these basic functions in
|
---|
226 | ready-made libraries. The major library on any Linux system is
|
---|
227 | <emphasis>Glibc</emphasis>.</para>
|
---|
228 |
|
---|
229 | <para>There are two primary ways of linking the functions from a library to a
|
---|
230 | program that uses them: statically or dynamically. When a program is linked
|
---|
231 | statically, the code of the used functions is included in the executable,
|
---|
232 | resulting in a rather bulky program. When a program is dynamically linked, what
|
---|
233 | is included is a reference to the dynamic linker, the name of the library, and
|
---|
234 | the name of the function, resulting in a much smaller executable. (A third way
|
---|
235 | is to use the programming interface of the dynamic linker. See the
|
---|
236 | <emphasis>dlopen</emphasis> man page for more information.)</para>
|
---|
237 |
|
---|
238 | <para>Dynamic linking is the default on Linux and has three major advantages
|
---|
239 | over static linking. First, you need only one copy of the executable library
|
---|
240 | code on your hard disk, instead of having many copies of the same code included
|
---|
241 | into a whole bunch of programs -- thus saving disk space. Second, when several
|
---|
242 | programs use the same library function at the same time, only one copy of the
|
---|
243 | function's code is required in core -- thus saving memory space. Third, when a
|
---|
244 | library function gets a bug fixed or is otherwise improved, you only need to
|
---|
245 | recompile this one library, instead of having to recompile all the programs that
|
---|
246 | make use of the improved function.</para>
|
---|
247 |
|
---|
248 | <para>If dynamic linking has several advantages, why then do we statically link
|
---|
249 | the first two packages in this chapter? The reasons are threefold: historical,
|
---|
250 | educational, and technical. Historical, because earlier versions of LFS
|
---|
251 | statically linked every program in this chapter. Educational, because knowing
|
---|
252 | the difference is useful. Technical, because we gain an element of independence
|
---|
253 | from the host in doing so, meaning that those programs can be used
|
---|
254 | independently of the host system. However, it's worth noting that an overall
|
---|
255 | successful LFS build can still be achieved when the first two packages are
|
---|
256 | built dynamically.</para>
|
---|
257 |
|
---|
258 | </sect2>
|
---|
259 |
|
---|
260 | </sect1>
|
---|
261 |
|
---|
262 |
|
---|
263 | <sect1 id="ch-tools-creatingtoolsdir">
|
---|
264 | <title>Creating the $LFS/tools directory</title>
|
---|
265 | <?dbhtml filename="creatingtoolsdir.html" dir="chapter05"?>
|
---|
266 |
|
---|
267 | <para>All programs compiled in this chapter will be installed under <filename
|
---|
268 | class="directory">$LFS/tools</filename> to keep them separate from the
|
---|
269 | programs compiled in the next chapter. The programs compiled here are only
|
---|
270 | temporary tools and won't be a part of the final LFS system and by keeping them
|
---|
271 | in a separate directory, we can later easily throw them away.</para>
|
---|
272 |
|
---|
273 | <para>Later on you might wish to search through the binaries of your system to
|
---|
274 | see what files they make use of or link against. To make this searching easier
|
---|
275 | you may want to choose a unique name for the directory in which the temporary
|
---|
276 | tools are stored. Instead of the simple "tools" you could use something like
|
---|
277 | "tools-for-lfs". However, you'll need to be careful to adjust all references to
|
---|
278 | "tools" throughout the book -- including those in any patches, notably the
|
---|
279 | GCC Specs Patch.</para>
|
---|
280 |
|
---|
281 | <para>Create the required directory by running the following:</para>
|
---|
282 |
|
---|
283 | <screen><userinput>mkdir $LFS/tools</userinput></screen>
|
---|
284 |
|
---|
285 | <para>The next step is to create a <filename>/tools</filename> symlink on
|
---|
286 | your host system. It will point to the directory we just created on the LFS
|
---|
287 | partition:</para>
|
---|
288 |
|
---|
289 | <screen><userinput>ln -s $LFS/tools /</userinput></screen>
|
---|
290 |
|
---|
291 | <note><para>The above command is correct. The <userinput>ln</userinput> command
|
---|
292 | has a few syntactic variations, so be sure to check the info page before
|
---|
293 | reporting what you may think is an error.</para></note>
|
---|
294 |
|
---|
295 | <para>The created symlink enables us to compile our toolchain so that it always
|
---|
296 | refers to <filename>/tools</filename>, meaning that the compiler, assembler
|
---|
297 | and linker will work both in this chapter (when we are still using some tools
|
---|
298 | from the host) <emphasis>and</emphasis> in the next (when we are chrooted to
|
---|
299 | the LFS partition).</para>
|
---|
300 |
|
---|
301 | </sect1>
|
---|
302 |
|
---|
303 |
|
---|
304 | <sect1 id="ch-tools-addinguser">
|
---|
305 | <title>Adding the user lfs</title>
|
---|
306 | <?dbhtml filename="addinguser.html" dir="chapter05"?>
|
---|
307 |
|
---|
308 | <para>When logged in as <emphasis>root</emphasis>, making a single mistake
|
---|
309 | can damage or even wreck your system. Therefore we recommend that you
|
---|
310 | build the packages in this chapter as an unprivileged user. You could
|
---|
311 | of course use your own user name, but to make it easier to set up a clean
|
---|
312 | work environment we'll create a new user <emphasis>lfs</emphasis> and
|
---|
313 | use this one during the installation process. As <emphasis>root</emphasis>,
|
---|
314 | issue the following commands to add the new user:</para>
|
---|
315 |
|
---|
316 | <screen><userinput>useradd -s /bin/bash -m -k /dev/null lfs
|
---|
317 | passwd lfs</userinput></screen>
|
---|
318 |
|
---|
319 | <para>The meaning of the switches:</para>
|
---|
320 |
|
---|
321 | <itemizedlist>
|
---|
322 | <listitem><para><userinput>-s /bin/bash</userinput>: This makes
|
---|
323 | <userinput>bash</userinput> the default shell for user
|
---|
324 | <emphasis>lfs</emphasis>.</para></listitem>
|
---|
325 |
|
---|
326 | <listitem><para><userinput>-m -k /dev/null</userinput>: These create a home
|
---|
327 | directory for <emphasis>lfs</emphasis>, while preventing the files from a
|
---|
328 | possible <filename>/etc/skel</filename> being copied into it.</para></listitem>
|
---|
329 | </itemizedlist>
|
---|
330 |
|
---|
331 | <para>Now grant this new user <emphasis>lfs</emphasis> full access to
|
---|
332 | <filename class="directory">$LFS/tools</filename> by giving it ownership
|
---|
333 | of the directory:</para>
|
---|
334 |
|
---|
335 | <screen><userinput>chown lfs $LFS/tools</userinput></screen>
|
---|
336 |
|
---|
337 | <para>If you made a separate working directory as suggested, give user
|
---|
338 | <emphasis>lfs</emphasis> ownership of this directory too:</para>
|
---|
339 |
|
---|
340 | <screen><userinput>chown lfs $LFS/sources</userinput></screen>
|
---|
341 |
|
---|
342 | <para>Next, login as user <emphasis>lfs</emphasis>. This can be done via a
|
---|
343 | virtual console, through a display manager, or with the following substitute
|
---|
344 | user command:</para>
|
---|
345 |
|
---|
346 | <screen><userinput>su - lfs</userinput></screen>
|
---|
347 |
|
---|
348 | <para>The "<userinput>-</userinput>" instructs <userinput>su</userinput> to
|
---|
349 | start a <emphasis>login</emphasis> shell.</para>
|
---|
350 |
|
---|
351 | </sect1>
|
---|
352 |
|
---|
353 |
|
---|
354 | <sect1 id="ch-tools-settingenviron">
|
---|
355 | <title>Setting up the environment</title>
|
---|
356 | <?dbhtml filename="settingenvironment.html" dir="chapter05"?>
|
---|
357 |
|
---|
358 | <para>We're going to set up a good working environment by creating two new
|
---|
359 | startup files for the <userinput>bash</userinput> shell. While logged in as
|
---|
360 | user <emphasis>lfs</emphasis>, issue the following command to create a new
|
---|
361 | <filename>.bash_profile</filename>:</para>
|
---|
362 |
|
---|
363 | <screen><userinput>cat > ~/.bash_profile << "EOF"</userinput>
|
---|
364 | exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
|
---|
365 | <userinput>EOF</userinput></screen>
|
---|
366 |
|
---|
367 | <para>Normally, when you log on as user <emphasis>lfs</emphasis>,
|
---|
368 | the initial shell is a <emphasis>login</emphasis> shell which reads the
|
---|
369 | <filename>/etc/profile</filename> of your host (probably containing some
|
---|
370 | settings of environment variables) and then <filename>.bash_profile</filename>.
|
---|
371 | The <userinput>exec env -i ... /bin/bash</userinput> command in the latter file
|
---|
372 | replaces the running shell with a new one with a completely empty environment,
|
---|
373 | except for the HOME, TERM and PS1 variables. This ensures that no unwanted and
|
---|
374 | potentially hazardous environment variables from the host system leak into our
|
---|
375 | build environment. The technique used here is a little strange, but it achieves
|
---|
376 | the goal of enforcing a clean environment.</para>
|
---|
377 |
|
---|
378 | <para>The new instance of the shell is a <emphasis>non-login</emphasis> shell,
|
---|
379 | which doesn't read the <filename>/etc/profile</filename> or
|
---|
380 | <filename>.bash_profile</filename> files, but reads the
|
---|
381 | <filename>.bashrc</filename> file instead. Create this latter file now:</para>
|
---|
382 |
|
---|
383 | <screen><userinput>cat > ~/.bashrc << "EOF"</userinput>
|
---|
384 | set +h
|
---|
385 | umask 022
|
---|
386 | LFS=/mnt/lfs
|
---|
387 | LC_ALL=POSIX
|
---|
388 | PATH=/tools/bin:/bin:/usr/bin
|
---|
389 | export LFS LC_ALL PATH
|
---|
390 | <userinput>EOF</userinput></screen>
|
---|
391 |
|
---|
392 | <para>The <userinput>set +h</userinput> command turns off
|
---|
393 | <userinput>bash</userinput>'s hash function. Normally hashing is a useful
|
---|
394 | feature: <userinput>bash</userinput> uses a hash table to remember the
|
---|
395 | full pathnames of executable files to avoid searching the PATH time and time
|
---|
396 | again to find the same executable. However, we'd like the new tools to be
|
---|
397 | used as soon as they are installed. By switching off the hash function, our
|
---|
398 | "interactive" commands (<userinput>make</userinput>,
|
---|
399 | <userinput>patch</userinput>, <userinput>sed</userinput>,
|
---|
400 | <userinput>cp</userinput> and so forth) will always use
|
---|
401 | the newest available version during the build process.</para>
|
---|
402 |
|
---|
403 | <para>Setting the user file-creation mask to 022 ensures that newly created
|
---|
404 | files and directories are only writable for their owner, but readable and
|
---|
405 | executable for anyone.</para>
|
---|
406 |
|
---|
407 | <para>The LFS variable should of course be set to the mount point you
|
---|
408 | chose.</para>
|
---|
409 |
|
---|
410 | <para>The LC_ALL variable controls the localization of certain programs,
|
---|
411 | making their messages follow the conventions of a specified country. If your
|
---|
412 | host system uses a version of Glibc older than 2.2.4,
|
---|
413 | having LC_ALL set to something other than "POSIX" or "C" during this chapter
|
---|
414 | may cause trouble if you exit the chroot environment and wish to return later.
|
---|
415 | By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that
|
---|
416 | everything will work as expected in the chroot environment.</para>
|
---|
417 |
|
---|
418 | <para>We prepend <filename>/tools/bin</filename> to the standard PATH so
|
---|
419 | that, as we move along through this chapter, the tools we build will get used
|
---|
420 | during the rest of the building process.</para>
|
---|
421 |
|
---|
422 | <para>Finally, to have our environment fully prepared for building the
|
---|
423 | temporary tools, source the just-created profile:</para>
|
---|
424 |
|
---|
425 | <screen><userinput>source ~/.bash_profile</userinput></screen>
|
---|
426 |
|
---|
427 | </sect1>
|
---|
428 |
|
---|
429 |
|
---|
430 | &c5-binutils-pass1;
|
---|
431 | &c5-gcc-pass1;
|
---|
432 | &c5-kernelheaders;
|
---|
433 | &c5-glibc;
|
---|
434 |
|
---|
435 |
|
---|
436 | <sect1 id="ch-tools-locking-glibc">
|
---|
437 | <title>"Locking in" Glibc</title>
|
---|
438 | <?dbhtml filename="lockingglibc.html" dir="chapter05"?>
|
---|
439 |
|
---|
440 | <para>Now that the temporary C libraries have been installed, we want all
|
---|
441 | the tools compiled in the rest of this chapter to be linked against these
|
---|
442 | libraries. To accomplish this, we need to adjust the linker and the compiler's
|
---|
443 | specs file.</para>
|
---|
444 |
|
---|
445 | <para>First install the adjusted linker by running the following from within
|
---|
446 | the <filename class="directory">binutils-build</filename> directory:</para>
|
---|
447 |
|
---|
448 | <screen><userinput>make -C ld install</userinput></screen>
|
---|
449 |
|
---|
450 | <para>The linker was adjusted a little while back, at the end of the first
|
---|
451 | pass of Binutils. From this point onwards everything will link <emphasis>only
|
---|
452 | </emphasis> against the libraries in <filename>/tools/lib</filename>.</para>
|
---|
453 |
|
---|
454 | <note><para>If you somehow missed the earlier warning to retain the Binutils
|
---|
455 | source and build directories from the first pass or otherwise accidentally
|
---|
456 | deleted them or just don't have access to them, don't worry, all is not lost.
|
---|
457 | Just ignore the above command. The result is a small chance of the subsequent
|
---|
458 | testing programs linking against libraries on the host. This is not ideal, but
|
---|
459 | it's not a major problem. The situation is corrected when we install the
|
---|
460 | second pass of Binutils a bit further on.</para></note>
|
---|
461 |
|
---|
462 | <para>Now that the adjusted linker is installed, you have to remove the
|
---|
463 | Binutils build and source directories.</para>
|
---|
464 |
|
---|
465 | <para>The next thing to do is to amend our GCC specs file so that it points
|
---|
466 | to the new dynamic linker. A simple sed will accomplish this:</para>
|
---|
467 |
|
---|
468 | <!-- Ampersands are needed to allow cut and paste -->
|
---|
469 |
|
---|
470 | <screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs &&
|
---|
471 | sed -e 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
|
---|
472 | $SPECFILE > tempspecfile &&
|
---|
473 | mv -f tempspecfile $SPECFILE &&
|
---|
474 | unset SPECFILE</userinput></screen>
|
---|
475 |
|
---|
476 | <para>We recommend that you cut-and-paste the above rather than try and type it
|
---|
477 | all in. Or you can edit the specs file by hand if you want to: just replace the
|
---|
478 | occurrence of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2". Be sure to
|
---|
479 | visually inspect the specs file to verify the intended change was actually
|
---|
480 | made.</para>
|
---|
481 |
|
---|
482 | <important><para>If you are working on a platform where the name of the dynamic
|
---|
483 | linker is something other than <filename>ld-linux.so.2</filename>, you
|
---|
484 | <emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the
|
---|
485 | name of your platform's dynamic linker in the above commands. Refer back to
|
---|
486 | <xref linkend="ch-tools-toolchaintechnotes"/> if necessary.</para></important>
|
---|
487 |
|
---|
488 | <para>Lastly, there is a possibility that some include files from the host
|
---|
489 | system have found their way into GCC's private include dir. This can happen
|
---|
490 | because of GCC's "fixincludes" process which runs as part of the GCC build.
|
---|
491 | We'll explain more about this further on in this chapter. For now, run the
|
---|
492 | following commands to eliminate this possibility:</para>
|
---|
493 |
|
---|
494 | <screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>
|
---|
495 |
|
---|
496 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
497 | <literallayout></literallayout>
|
---|
498 |
|
---|
499 | <caution><para>It is imperative at this point to stop and ensure that the basic
|
---|
500 | functions (compiling and linking) of the new toolchain are working as expected.
|
---|
501 | For this we are going to perform a simple sanity check:</para>
|
---|
502 |
|
---|
503 | <screen><userinput>echo 'main(){}' > dummy.c
|
---|
504 | cc dummy.c
|
---|
505 | readelf -l a.out | grep ': /tools'</userinput></screen>
|
---|
506 |
|
---|
507 | <para>If everything is working correctly, there should be no errors, and the
|
---|
508 | output of the last command will be:</para>
|
---|
509 |
|
---|
510 | <blockquote><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</screen></blockquote>
|
---|
511 |
|
---|
512 | <para>(Of course allowing for platform specific differences in dynamic linker
|
---|
513 | name). Note especially that <filename class="directory">/tools/lib</filename>
|
---|
514 | appears as the prefix of our dynamic linker. If you did not receive the output
|
---|
515 | as shown above, or received no output at all, then something is seriously wrong.
|
---|
516 | You will need to investigate and retrace your steps to find out where the
|
---|
517 | problem is and correct it. There is no point in continuing until this is done.
|
---|
518 | First, redo the sanity check using <userinput>gcc</userinput> instead of
|
---|
519 | <userinput>cc</userinput>. If this works it means the
|
---|
520 | <filename class="symlink">/tools/bin/cc</filename> symlink is missing. Revisit
|
---|
521 | <xref linkend="ch-tools-gcc-pass1"/> and fix the symlink. Second, ensure your $PATH
|
---|
522 | is correct. You can check this by running <userinput>echo $PATH</userinput> and
|
---|
523 | verifying that <filename class="directory">/tools/bin</filename> is at the head
|
---|
524 | of the list. If the $PATH is wrong it could mean you're not logged in as user
|
---|
525 | <emphasis>lfs</emphasis> or something went wrong back in
|
---|
526 | <xref linkend="ch-tools-settingenviron"/>. Third, something may have gone wrong with
|
---|
527 | the specs file amendment above. In this case redo the specs file amendment
|
---|
528 | ensuring to cut-and-paste the commands as was recommended.</para>
|
---|
529 |
|
---|
530 | <para>Once you are satisfied that all is well, clean up the test files:</para>
|
---|
531 |
|
---|
532 | <screen><userinput>rm dummy.c a.out</userinput></screen>
|
---|
533 | </caution>
|
---|
534 |
|
---|
535 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
536 | <literallayout></literallayout>
|
---|
537 |
|
---|
538 | <para>This completes the installation of the self-contained toolchain, and it
|
---|
539 | can now be used to build the rest of the temporary tools.</para>
|
---|
540 |
|
---|
541 | </sect1>
|
---|
542 |
|
---|
543 |
|
---|
544 | &c5-tcl;
|
---|
545 | &c5-expect;
|
---|
546 | &c5-dejagnu;
|
---|
547 | &c5-gcc-pass2;
|
---|
548 | &c5-binutils-pass2;
|
---|
549 |
|
---|
550 | &c5-gawk;
|
---|
551 | &c5-coreutils;
|
---|
552 | &c5-bzip2;
|
---|
553 | &c5-gzip;
|
---|
554 | &c5-diffutils;
|
---|
555 | &c5-findutils;
|
---|
556 | &c5-make;
|
---|
557 | &c5-grep;
|
---|
558 | &c5-sed;
|
---|
559 | &c5-gettext;
|
---|
560 | &c5-ncurses;
|
---|
561 | &c5-patch;
|
---|
562 | &c5-tar;
|
---|
563 | &c5-texinfo;
|
---|
564 | &c5-bash;
|
---|
565 | &c5-utillinux;
|
---|
566 | &c5-perl;
|
---|
567 |
|
---|
568 |
|
---|
569 | <sect1 id="ch-tools-stripping">
|
---|
570 | <title>Stripping</title>
|
---|
571 | <?dbhtml filename="stripping.html" dir="chapter05"?>
|
---|
572 |
|
---|
573 | <para>The steps in this section are optional. If your LFS partition is rather
|
---|
574 | small, you will be glad to learn that you can throw away some unnecessary
|
---|
575 | things. The executables and libraries you have built so far contain about 130 MB
|
---|
576 | of unneeded debugging symbols. Remove those symbols like this:</para>
|
---|
577 |
|
---|
578 | <screen><userinput>strip --strip-unneeded /tools/{,s}bin/*
|
---|
579 | strip --strip-debug /tools/lib/*</userinput></screen>
|
---|
580 |
|
---|
581 | <para>The first of the above commands will skip some twenty files, reporting
|
---|
582 | that it doesn't recognize their file format. Most of them are scripts instead
|
---|
583 | of binaries.</para>
|
---|
584 |
|
---|
585 | <para>Take care <emphasis>not</emphasis> to use
|
---|
586 | <userinput>--strip-unneeded</userinput> on the libraries -- they would be
|
---|
587 | destroyed and you would have to build Glibc all over again.</para>
|
---|
588 |
|
---|
589 | <para>To save another couple of megabytes, you can throw away all the
|
---|
590 | documentation:</para>
|
---|
591 |
|
---|
592 | <screen><userinput>rm -rf /tools/{,share/}{doc,info,man}</userinput></screen>
|
---|
593 |
|
---|
594 | <para>You will now need to have at least 850 MB of free space on your LFS
|
---|
595 | filesystem to be able to build and install Glibc in the next phase. If you can
|
---|
596 | build and install Glibc, you can build and install the rest too.</para>
|
---|
597 |
|
---|
598 | </sect1>
|
---|
599 |
|
---|
600 | </chapter>
|
---|
601 |
|
---|