[98c95f5] | 1 | <sect1 id="ch05-toolchaintechnotes">
|
---|
| 2 | <title>Toolchain technical notes</title>
|
---|
| 3 | <?dbhtml filename="toolchaintechnotes.html" dir="chapter05"?>
|
---|
| 4 |
|
---|
| 5 | <para>This section attempts to explain some of the rationale and technical
|
---|
| 6 | details behind the overall build method. It's not essential that you understand
|
---|
| 7 | everything here immediately. Most of it will make sense once you have performed
|
---|
| 8 | an actual build. Feel free to refer back here at any time.</para>
|
---|
| 9 |
|
---|
| 10 | <para>The overall goal of Chapter 5 is to provide a sane, temporary environment
|
---|
| 11 | that we can chroot into, and from which we can produce a clean, trouble-free
|
---|
| 12 | build of the target LFS system in Chapter 6. Along the way, we attempt to
|
---|
| 13 | divorce ourselves from the host system as much as possible, and in so doing
|
---|
| 14 | build a self-contained and self-hosted toolchain. It should be noted that the
|
---|
| 15 | build process has been designed in such a way so as to minimize the risks for
|
---|
| 16 | new readers and also provide maximum educational value at the same time. In
|
---|
| 17 | other words, more advanced techniques could be used to achieve the same
|
---|
| 18 | goals.</para>
|
---|
| 19 |
|
---|
| 20 | <important>
|
---|
| 21 | <para>Before continuing, you really should be aware of the name of your working
|
---|
| 22 | platform, often also referred to as the <emphasis>target triplet</emphasis>. For
|
---|
| 23 | many folks the target triplet will be, for example:
|
---|
| 24 | <emphasis>i686-pc-linux-gnu</emphasis>. A simple way to determine your target
|
---|
| 25 | triplet is to run the <filename>config.guess</filename> script that comes with
|
---|
| 26 | the source for many packages. Unpack the Binutils sources and run the script:
|
---|
| 27 | <userinput>./config.guess</userinput> and note the output.</para>
|
---|
| 28 |
|
---|
| 29 | <para>You'll also need to be aware of the name of your platform's
|
---|
| 30 | <emphasis>dynamic linker</emphasis>, often also referred to as the
|
---|
| 31 | <emphasis>dynamic loader</emphasis>, not to be confused with the standard linker
|
---|
| 32 | <emphasis>ld</emphasis> that is part of Binutils. The dynamic linker is provided
|
---|
| 33 | by Glibc and has the job of finding and loading the shared libraries needed by a
|
---|
| 34 | program, preparing the program to run and then running it. For most folks, the
|
---|
| 35 | name of the dynamic linker will be <emphasis>ld-linux.so.2</emphasis>. On
|
---|
| 36 | platforms that are less prevalent, the name might be
|
---|
| 37 | <emphasis>ld.so.1</emphasis> and newer 64 bit platforms might even have
|
---|
| 38 | something completely different. You should be able to determine the name
|
---|
| 39 | of your platform's dynamic linker by looking in the
|
---|
| 40 | <filename class="directory">/lib</filename> directory on your host system. A
|
---|
| 41 | surefire way is to inspect a random binary from your host system by running:
|
---|
| 42 | <userinput>`readelf -l <name of binary> | grep interpreter`</userinput>
|
---|
| 43 | and noting the output. The authoritative reference covering all platforms is in
|
---|
| 44 | the <filename>shlib-versions</filename> file in the root of the Glibc source
|
---|
| 45 | tree.</para>
|
---|
| 46 | </important>
|
---|
| 47 |
|
---|
| 48 | <para>Some key technical points of how the Chapter 5 build method works:</para>
|
---|
| 49 |
|
---|
| 50 | <itemizedlist>
|
---|
| 51 | <listitem><para>Similar in principle to cross compiling whereby tools installed
|
---|
| 52 | into the same prefix work in cooperation and thus utilize a little GNU
|
---|
| 53 | "magic".</para></listitem>
|
---|
| 54 |
|
---|
| 55 | <listitem><para>Careful manipulation of the standard linker's library search
|
---|
| 56 | path to ensure programs are linked only against libraries we
|
---|
| 57 | choose.</para></listitem>
|
---|
| 58 |
|
---|
| 59 | <listitem><para>Careful manipulation of GCC's <emphasis>specs</emphasis> file to
|
---|
| 60 | tell GCC which target dynamic linker will be used.</para></listitem>
|
---|
| 61 | </itemizedlist>
|
---|
| 62 |
|
---|
| 63 | <para>Binutils is installed first because both GCC and Glibc perform various
|
---|
| 64 | feature tests on the assembler and linker during their respective runs of
|
---|
| 65 | <filename>./configure</filename> to determine which software features to enable
|
---|
| 66 | or disable. This is more important than one might first realize. An incorrectly
|
---|
| 67 | configured GCC or Glibc can result in a subtly broken toolchain where the impact
|
---|
| 68 | of such breakage might not show up until near the end of a build of a whole
|
---|
| 69 | distribution. Thankfully, a test suite failure will usually alert us before too
|
---|
| 70 | much harm is done.</para>
|
---|
| 71 |
|
---|
| 72 | <para>Binutils installs its assembler and linker into two locations,
|
---|
| 73 | <filename class="directory">/tools/bin</filename> and
|
---|
| 74 | <filename class="directory">/tools/$TARGET_TRIPLET/bin</filename>. In reality,
|
---|
| 75 | the tools in one location are hard linked to the other. An important facet of ld
|
---|
| 76 | is its library search order. Detailed information can be obtained from ld by
|
---|
| 77 | passing it the <emphasis>--verbose</emphasis> flag. For example:
|
---|
| 78 | <userinput>`ld --verbose | grep SEARCH`</userinput> will show you the current
|
---|
| 79 | search paths and order. You can see what files are actually linked by ld by
|
---|
| 80 | compiling a dummy program and passing the --verbose switch. For example:
|
---|
| 81 | <userinput>`gcc dummy.c -Wl,--verbose 2>&1 | grep succeeded`</userinput>
|
---|
| 82 | will show you all the files successfully opened during the link.</para>
|
---|
| 83 |
|
---|
| 84 | <para>The next package installed is GCC and during its run of
|
---|
| 85 | <filename>./configure</filename> you'll see, for example:</para>
|
---|
| 86 |
|
---|
| 87 | <blockquote><screen>checking what assembler to use... /tools/i686-pc-linux-gnu/bin/as
|
---|
| 88 | checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</screen></blockquote>
|
---|
| 89 |
|
---|
| 90 | <para>This is important for the reasons mentioned above. It also demonstrates
|
---|
| 91 | that GCC's configure script does not search the $PATH directories to find which
|
---|
| 92 | tools to use. However, during the actual operation of GCC itself, the same
|
---|
| 93 | search paths are not necessarily used. You can find out which standard linker
|
---|
| 94 | GCC will use by running: <userinput>`gcc -print-prog-name=ld`</userinput>.
|
---|
| 95 | Detailed information can be obtained from GCC by passing it the
|
---|
| 96 | <emphasis>-v</emphasis> flag while compiling a dummy program. For example:
|
---|
| 97 | <userinput>`gcc -v dummy.c`</userinput> will show you detailed information about
|
---|
| 98 | the preprocessor, compilation and assembly stages, including GCC's include
|
---|
| 99 | search paths and order.</para>
|
---|
| 100 |
|
---|
| 101 | <para>The next package installed is Glibc. The most important considerations for
|
---|
| 102 | building Glibc are the compiler, binary tools and kernel headers. The compiler
|
---|
| 103 | is generally no problem as it will always use the GCC found in a $PATH
|
---|
| 104 | directory. The binary tools and kernel headers can be a little more troublesome.
|
---|
| 105 | Therefore we take no risks and we use the available configure switches to
|
---|
| 106 | enforce the correct selections. After the run of
|
---|
| 107 | <filename>./configure</filename> you can check the contents of the
|
---|
| 108 | <filename>config.make</filename> file in the
|
---|
| 109 | <filename class="directory">glibc-build</filename> directory for all the
|
---|
| 110 | important details. You'll note some interesting items like the use of
|
---|
| 111 | <userinput>CC="gcc -B/tools/bin/"</userinput> to control which binary tools are
|
---|
| 112 | used and also the use of the <emphasis>-nostdinc</emphasis> and
|
---|
| 113 | <emphasis>-isystem</emphasis> flags to control the GCC include search path.
|
---|
| 114 | These items help to highlight an important aspect of the Glibc package: it is
|
---|
| 115 | very self sufficient in terms of its build machinery and generally does not rely
|
---|
| 116 | on toolchain defaults.</para>
|
---|
| 117 |
|
---|
| 118 | <para>After the Glibc installation, we make some adjustments to ensure that
|
---|
| 119 | searching and linking take place only within our /tools prefix. We install an
|
---|
| 120 | adjusted ld, which has a hard-wired search path limited to
|
---|
| 121 | <filename class="directory">/tools/lib</filename>. Then we amend GCC's specs
|
---|
| 122 | file to point to our new dynamic linker in
|
---|
| 123 | <filename class="directory">/tools/lib</filename>. This last step is
|
---|
| 124 | <emphasis>vital</emphasis> to the whole process. As mentioned above, a
|
---|
[f57e3d1] | 125 | hard-wired path to a dynamic linker is embedded into every ELF shared
|
---|
| 126 | executable. You can inspect this by running:
|
---|
[98c95f5] | 127 | <userinput>`readelf -l <name of binary> | grep interpreter`</userinput>.
|
---|
| 128 | By amending the GCC specs file, we are ensuring that every program compiled from
|
---|
| 129 | here through the end of Chapter 5 will use our new dynamic linker in
|
---|
| 130 | <filename class="directory">/tools/lib</filename>.</para>
|
---|
| 131 |
|
---|
| 132 | <para>The need to use the new dynamic linker is also the reason why we apply the
|
---|
| 133 | specs patch for the second pass of GCC. Failure to do so will result in the GCC
|
---|
| 134 | programs themselves having the dynamic linker from the host system's
|
---|
| 135 | <filename class="directory">/lib</filename> directory embedded into them, which
|
---|
| 136 | would defeat our goal of getting away from the host system.</para>
|
---|
| 137 |
|
---|
| 138 | <para>During the second pass of Binutils, we are able to utilize the
|
---|
| 139 | <userinput>--with-lib-path</userinput> configure switch to control ld's library
|
---|
| 140 | search path. From this point onwards, the core toolchain is self-contained and
|
---|
| 141 | self-hosted. The remainder of the Chapter 5 packages all build against the new
|
---|
| 142 | Glibc in <filename class="directory">/tools</filename> and all is well.</para>
|
---|
| 143 |
|
---|
| 144 | <para>Upon entering the chroot environment in Chapter 6, the first major package
|
---|
| 145 | we install is Glibc, due to its self sufficient nature that we mentioned above.
|
---|
| 146 | Once this Glibc is installed into <filename class="directory">/usr</filename>,
|
---|
| 147 | we perform a quick changeover of the toolchain defaults, then proceed for real
|
---|
| 148 | in building the rest of the target Chapter 6 LFS system.</para>
|
---|
| 149 |
|
---|
| 150 | <sect2>
|
---|
| 151 | <title>Notes on static linking</title>
|
---|
| 152 |
|
---|
| 153 | <para>Most programs have to perform, beside their specific task, many rather
|
---|
[8b437193] | 154 | common and sometimes trivial operations. These include allocating memory,
|
---|
[98c95f5] | 155 | searching directories, reading and writing files, string handling, pattern
|
---|
[8b437193] | 156 | matching, arithmetic and many other tasks. Instead of obliging each program to
|
---|
[98c95f5] | 157 | reinvent the wheel, the GNU system provides all these basic functions in
|
---|
| 158 | ready-made libraries. The major library on any Linux system is
|
---|
| 159 | <emphasis>Glibc</emphasis>.</para>
|
---|
| 160 |
|
---|
| 161 | <para>There are two primary ways of linking the functions from a library to a
|
---|
| 162 | program that uses them: statically or dynamically. When a program is linked
|
---|
| 163 | statically, the code of the used functions is included in the executable,
|
---|
| 164 | resulting in a rather bulky program. When a program is dynamically linked, what
|
---|
| 165 | is included is a reference to the dynamic linker, the name of the library, and
|
---|
| 166 | the name of the function, resulting in a much smaller executable. A third way is
|
---|
| 167 | to use the programming interface of the dynamic linker. See the
|
---|
| 168 | <emphasis>dlopen</emphasis> man page for more information.</para>
|
---|
| 169 |
|
---|
| 170 | <para>Dynamic linking is the default on Linux and has three major advantages
|
---|
| 171 | over static linking. First, you need only one copy of the executable library
|
---|
| 172 | code on your hard disk, instead of having many copies of the same code included
|
---|
| 173 | into a whole bunch of programs -- thus saving disk space. Second, when several
|
---|
| 174 | programs use the same library function at the same time, only one copy of the
|
---|
| 175 | function's code is required in core -- thus saving memory space. Third, when a
|
---|
| 176 | library function gets a bug fixed or is otherwise improved, you only need to
|
---|
| 177 | recompile this one library, instead of having to recompile all the programs that
|
---|
| 178 | make use of the improved function.</para>
|
---|
| 179 |
|
---|
| 180 | <para>Why do we statically link the first two packages in Chapter 5? The reasons
|
---|
| 181 | are threefold: historical, educational and technical. Historical because earlier
|
---|
| 182 | versions of LFS statically linked every program in Chapter 5. Educational
|
---|
| 183 | because knowing the difference is useful. Technical because we gain an element
|
---|
| 184 | of independence from the host in doing so, i.e. those programs can be used
|
---|
| 185 | independently of the host system. However, it's worth noting that an overall
|
---|
| 186 | successful LFS build can still be achieved when the first two packages are built
|
---|
| 187 | dynamically.</para>
|
---|
| 188 |
|
---|
| 189 | </sect2>
|
---|
| 190 |
|
---|
| 191 | </sect1>
|
---|
| 192 |
|
---|