[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[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 | ]>
|
---|
[b28fd35] | 7 |
|
---|
[6481cf9] | 8 | <sect1 id="ch-tools-toolchaintechnotes" xreflabel="Toolchain Technical Notes">
|
---|
[b28fd35] | 9 | <?dbhtml filename="toolchaintechnotes.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Toolchain Technical Notes</title>
|
---|
| 12 |
|
---|
| 13 | <para>This section explains some of the rationale and technical details
|
---|
[5620622] | 14 | behind the overall build method. Don't try to immediately
|
---|
[b28fd35] | 15 | understand everything in this section. Most of this information will be
|
---|
[5620622] | 16 | clearer after performing an actual build. Come back and re-read this chapter
|
---|
| 17 | at any time during the build process.</para>
|
---|
[b28fd35] | 18 |
|
---|
[80f8c02] | 19 | <para>The overall goal of <xref linkend="chapter-cross-tools"/> and <xref
|
---|
[5620622] | 20 | linkend="chapter-temporary-tools"/> is to produce a temporary area
|
---|
| 21 | containing a set of tools that are known to be good, and that are isolated from the host system.
|
---|
| 22 | By using the <command>chroot</command> command, the compilations in the remaining chapters
|
---|
| 23 | will be isolated within that environment, ensuring a clean, trouble-free
|
---|
[79524a0] | 24 | build of the target LFS system. The build process has been designed to
|
---|
[5620622] | 25 | minimize the risks for new readers, and to provide the most educational value
|
---|
[79524a0] | 26 | at the same time.</para>
|
---|
[b28fd35] | 27 |
|
---|
[5620622] | 28 | <para>This build process is based on
|
---|
[efcb393] | 29 | <emphasis>cross-compilation</emphasis>. Cross-compilation is normally used
|
---|
[5620622] | 30 | to build a compiler and its associated toolchain for a machine different from
|
---|
| 31 | the one that is used for the build. This is not strictly necessary for LFS,
|
---|
[efcb393] | 32 | since the machine where the new system will run is the same as the one
|
---|
[5620622] | 33 | used for the build. But cross-compilation has one great advantage:
|
---|
[efcb393] | 34 | anything that is cross-compiled cannot depend on the host environment.</para>
|
---|
| 35 |
|
---|
| 36 | <sect2 id="cross-compile" xreflabel="About Cross-Compilation">
|
---|
| 37 |
|
---|
| 38 | <title>About Cross-Compilation</title>
|
---|
| 39 |
|
---|
[d48d1c2] | 40 | <note>
|
---|
| 41 | <para>
|
---|
[5620622] | 42 | The LFS book is not (and does not contain) a general tutorial to
|
---|
| 43 | build a cross (or native) toolchain. Don't use the commands in the
|
---|
| 44 | book for a cross toolchain for some purpose other
|
---|
[d48d1c2] | 45 | than building LFS, unless you really understand what you are doing.
|
---|
| 46 | </para>
|
---|
| 47 | </note>
|
---|
| 48 |
|
---|
[5620622] | 49 | <para>Cross-compilation involves some concepts that deserve a section of
|
---|
| 50 | their own. Although this section may be omitted on a first reading,
|
---|
| 51 | coming back to it later will help you gain a fuller understanding of
|
---|
[7e62bbc] | 52 | the process.</para>
|
---|
[efcb393] | 53 |
|
---|
[5620622] | 54 | <para>Let us first define some terms used in this context.</para>
|
---|
[efcb393] | 55 |
|
---|
| 56 | <variablelist>
|
---|
[5620622] | 57 | <varlistentry><term>The build</term><listitem>
|
---|
[efcb393] | 58 | <para>is the machine where we build programs. Note that this machine
|
---|
[5620622] | 59 | is also referred to as the <quote>host</quote>.</para></listitem>
|
---|
[efcb393] | 60 | </varlistentry>
|
---|
| 61 |
|
---|
[5620622] | 62 | <varlistentry><term>The host</term><listitem>
|
---|
[efcb393] | 63 | <para>is the machine/system where the built programs will run. Note
|
---|
| 64 | that this use of <quote>host</quote> is not the same as in other
|
---|
| 65 | sections.</para></listitem>
|
---|
| 66 | </varlistentry>
|
---|
| 67 |
|
---|
[5620622] | 68 | <varlistentry><term>The target</term><listitem>
|
---|
[efcb393] | 69 | <para>is only used for compilers. It is the machine the compiler
|
---|
[5620622] | 70 | produces code for. It may be different from both the build and
|
---|
| 71 | the host.</para></listitem>
|
---|
[efcb393] | 72 | </varlistentry>
|
---|
| 73 |
|
---|
| 74 | </variablelist>
|
---|
| 75 |
|
---|
[c3471cf] | 76 | <para>As an example, let us imagine the following scenario (sometimes
|
---|
[5620622] | 77 | referred to as <quote>Canadian Cross</quote>): we have a
|
---|
[7e62bbc] | 78 | compiler on a slow machine only, let's call it machine A, and the compiler
|
---|
[5620622] | 79 | ccA. We also have a fast machine (B), but no compiler for (B), and we
|
---|
| 80 | want to produce code for a third, slow machine (C). We will build a
|
---|
| 81 | compiler for machine C in three stages.</para>
|
---|
[efcb393] | 82 |
|
---|
| 83 | <informaltable align="center">
|
---|
| 84 | <tgroup cols="5">
|
---|
| 85 | <colspec colnum="1" align="center"/>
|
---|
| 86 | <colspec colnum="2" align="center"/>
|
---|
| 87 | <colspec colnum="3" align="center"/>
|
---|
| 88 | <colspec colnum="4" align="center"/>
|
---|
| 89 | <colspec colnum="5" align="left"/>
|
---|
| 90 | <thead>
|
---|
| 91 | <row><entry>Stage</entry><entry>Build</entry><entry>Host</entry>
|
---|
| 92 | <entry>Target</entry><entry>Action</entry></row>
|
---|
| 93 | </thead>
|
---|
| 94 | <tbody>
|
---|
| 95 | <row>
|
---|
| 96 | <entry>1</entry><entry>A</entry><entry>A</entry><entry>B</entry>
|
---|
[5620622] | 97 | <entry>Build cross-compiler cc1 using ccA on machine A.</entry>
|
---|
[efcb393] | 98 | </row>
|
---|
| 99 | <row>
|
---|
[c3471cf] | 100 | <entry>2</entry><entry>A</entry><entry>B</entry><entry>C</entry>
|
---|
[5620622] | 101 | <entry>Build cross-compiler cc2 using cc1 on machine A.</entry>
|
---|
[efcb393] | 102 | </row>
|
---|
| 103 | <row>
|
---|
| 104 | <entry>3</entry><entry>B</entry><entry>C</entry><entry>C</entry>
|
---|
[5620622] | 105 | <entry>Build compiler ccC using cc2 on machine B.</entry>
|
---|
[efcb393] | 106 | </row>
|
---|
| 107 | </tbody>
|
---|
| 108 | </tgroup>
|
---|
| 109 | </informaltable>
|
---|
| 110 |
|
---|
[5620622] | 111 | <para>Then, all the programs needed by machine C can be compiled
|
---|
[efcb393] | 112 | using cc2 on the fast machine B. Note that unless B can run programs
|
---|
[5620622] | 113 | produced for C, there is no way to test the newly built programs until machine
|
---|
| 114 | C itself is running. For example, to run a test suite on ccC, we may want to add a
|
---|
[efcb393] | 115 | fourth stage:</para>
|
---|
| 116 |
|
---|
| 117 | <informaltable align="center">
|
---|
| 118 | <tgroup cols="5">
|
---|
| 119 | <colspec colnum="1" align="center"/>
|
---|
| 120 | <colspec colnum="2" align="center"/>
|
---|
| 121 | <colspec colnum="3" align="center"/>
|
---|
| 122 | <colspec colnum="4" align="center"/>
|
---|
| 123 | <colspec colnum="5" align="left"/>
|
---|
| 124 | <thead>
|
---|
| 125 | <row><entry>Stage</entry><entry>Build</entry><entry>Host</entry>
|
---|
| 126 | <entry>Target</entry><entry>Action</entry></row>
|
---|
| 127 | </thead>
|
---|
| 128 | <tbody>
|
---|
| 129 | <row>
|
---|
| 130 | <entry>4</entry><entry>C</entry><entry>C</entry><entry>C</entry>
|
---|
[5620622] | 131 | <entry>Rebuild and test ccC using ccC on machine C.</entry>
|
---|
[efcb393] | 132 | </row>
|
---|
| 133 | </tbody>
|
---|
| 134 | </tgroup>
|
---|
| 135 | </informaltable>
|
---|
| 136 |
|
---|
| 137 | <para>In the example above, only cc1 and cc2 are cross-compilers, that is,
|
---|
| 138 | they produce code for a machine different from the one they are run on.
|
---|
| 139 | The other compilers ccA and ccC produce code for the machine they are run
|
---|
| 140 | on. Such compilers are called <emphasis>native</emphasis> compilers.</para>
|
---|
| 141 |
|
---|
| 142 | </sect2>
|
---|
| 143 |
|
---|
| 144 | <sect2 id="lfs-cross">
|
---|
| 145 | <title>Implementation of Cross-Compilation for LFS</title>
|
---|
| 146 |
|
---|
| 147 | <note>
|
---|
[e18ba69] | 148 | <para>All packages involved with cross compilation in the book use an
|
---|
| 149 | autoconf-based building system. The autoconf-based building system
|
---|
| 150 | accepts system types in the form cpu-vendor-kernel-os,
|
---|
| 151 | referred to as the system triplet. Since the vendor field is mostly
|
---|
| 152 | irrelevant, autoconf allows to omit it. An astute reader may wonder
|
---|
| 153 | why a <quote>triplet</quote> refers to a four component name. The
|
---|
[b3daf01] | 154 | reason is the kernel field and the os field originated from one
|
---|
[e18ba69] | 155 | <quote>system</quote> field. Such a three-field form is still valid
|
---|
| 156 | today for some systems, for example
|
---|
| 157 | <literal>x86_64-unknown-freebsd</literal>. But for other systems,
|
---|
| 158 | two systems can share the same kernel but still be too different to
|
---|
| 159 | use a same triplet for them. For example, an Android running on a
|
---|
| 160 | mobile phone is completely different from Ubuntu running on an ARM64
|
---|
[77b46db] | 161 | server, despite they are running on the same type of CPU (ARM64) and
|
---|
| 162 | using the same kernel (Linux).
|
---|
| 163 | Without an emulation layer, you cannot run an
|
---|
| 164 | executable for the server on the mobile phone or vice versa. So the
|
---|
[e18ba69] | 165 | <quote>system</quote> field is separated into kernel and os fields to
|
---|
| 166 | designate these systems unambiguously. For our example, the Android
|
---|
| 167 | system is designated <literal>aarch64-unknown-linux-android</literal>,
|
---|
| 168 | and the Ubuntu system is designated
|
---|
| 169 | <literal>aarch64-unknown-linux-gnu</literal>. The word
|
---|
| 170 | <quote>triplet</quote> remained. A simple way to determine your
|
---|
| 171 | system triplet is to run the <command>config.guess</command>
|
---|
[79524a0] | 172 | script that comes with the source for many packages. Unpack the binutils
|
---|
[efcb393] | 173 | sources and run the script: <userinput>./config.guess</userinput> and note
|
---|
| 174 | the output. For example, for a 32-bit Intel processor the
|
---|
| 175 | output will be <emphasis>i686-pc-linux-gnu</emphasis>. On a 64-bit
|
---|
[5620622] | 176 | system it will be <emphasis>x86_64-pc-linux-gnu</emphasis>. On most
|
---|
| 177 | Linux systems the even simpler <command>gcc -dumpmachine</command> command
|
---|
[3c4e129] | 178 | will give you similar information.</para>
|
---|
[efcb393] | 179 |
|
---|
[5620622] | 180 | <para>You should also be aware of the name of the platform's dynamic linker, often
|
---|
[efcb393] | 181 | referred to as the dynamic loader (not to be confused with the standard
|
---|
[79524a0] | 182 | linker <command>ld</command> that is part of binutils). The dynamic linker
|
---|
[5620622] | 183 | provided by package glibc finds and loads the shared libraries needed by a
|
---|
[efcb393] | 184 | program, prepares the program to run, and then runs it. The name of the
|
---|
[7e62bbc] | 185 | dynamic linker for a 32-bit Intel machine is <filename
|
---|
[5620622] | 186 | class="libraryfile">ld-linux.so.2</filename>; it's <filename
|
---|
| 187 | class="libraryfile">ld-linux-x86-64.so.2</filename> on 64-bit systems. A
|
---|
[efcb393] | 188 | sure-fire way to determine the name of the dynamic linker is to inspect a
|
---|
| 189 | random binary from the host system by running: <userinput>readelf -l
|
---|
| 190 | <name of binary> | grep interpreter</userinput> and noting the
|
---|
| 191 | output. The authoritative reference covering all platforms is in the
|
---|
[5620622] | 192 | <filename>shlib-versions</filename> file in the root of the glibc source
|
---|
[efcb393] | 193 | tree.</para>
|
---|
| 194 | </note>
|
---|
| 195 |
|
---|
[7e62bbc] | 196 | <para>In order to fake a cross compilation in LFS, the name of the host triplet
|
---|
[efcb393] | 197 | is slightly adjusted by changing the "vendor" field in the
|
---|
[5620622] | 198 | <envar>LFS_TGT</envar> variable so it says "lfs". We also use the
|
---|
[79524a0] | 199 | <parameter>--with-sysroot</parameter> option when building the cross linker and
|
---|
| 200 | cross compiler to tell them where to find the needed host files. This
|
---|
| 201 | ensures that none of the other programs built in <xref
|
---|
[efcb393] | 202 | linkend="chapter-temporary-tools"/> can link to libraries on the build
|
---|
[5620622] | 203 | machine. Only two stages are mandatory, plus one more for tests.</para>
|
---|
[efcb393] | 204 |
|
---|
| 205 | <informaltable align="center">
|
---|
| 206 | <tgroup cols="5">
|
---|
| 207 | <colspec colnum="1" align="center"/>
|
---|
| 208 | <colspec colnum="2" align="center"/>
|
---|
| 209 | <colspec colnum="3" align="center"/>
|
---|
| 210 | <colspec colnum="4" align="center"/>
|
---|
| 211 | <colspec colnum="5" align="left"/>
|
---|
| 212 | <thead>
|
---|
| 213 | <row><entry>Stage</entry><entry>Build</entry><entry>Host</entry>
|
---|
| 214 | <entry>Target</entry><entry>Action</entry></row>
|
---|
| 215 | </thead>
|
---|
| 216 | <tbody>
|
---|
| 217 | <row>
|
---|
| 218 | <entry>1</entry><entry>pc</entry><entry>pc</entry><entry>lfs</entry>
|
---|
[5620622] | 219 | <entry>Build cross-compiler cc1 using cc-pc on pc.</entry>
|
---|
[efcb393] | 220 | </row>
|
---|
| 221 | <row>
|
---|
| 222 | <entry>2</entry><entry>pc</entry><entry>lfs</entry><entry>lfs</entry>
|
---|
[5620622] | 223 | <entry>Build compiler cc-lfs using cc1 on pc.</entry>
|
---|
[efcb393] | 224 | </row>
|
---|
| 225 | <row>
|
---|
| 226 | <entry>3</entry><entry>lfs</entry><entry>lfs</entry><entry>lfs</entry>
|
---|
[5620622] | 227 | <entry>Rebuild and test cc-lfs using cc-lfs on lfs.</entry>
|
---|
[efcb393] | 228 | </row>
|
---|
| 229 | </tbody>
|
---|
| 230 | </tgroup>
|
---|
| 231 | </informaltable>
|
---|
| 232 |
|
---|
[5620622] | 233 | <para>In the preceding table, <quote>on pc</quote> means the commands are run
|
---|
[efcb393] | 234 | on a machine using the already installed distribution. <quote>On
|
---|
| 235 | lfs</quote> means the commands are run in a chrooted environment.</para>
|
---|
| 236 |
|
---|
| 237 | <para>Now, there is more about cross-compiling: the C language is not
|
---|
| 238 | just a compiler, but also defines a standard library. In this book, the
|
---|
[5620622] | 239 | GNU C library, named glibc, is used (there is an alternative, "musl"). This library must
|
---|
| 240 | be compiled for the LFS machine; that is, using the cross compiler cc1.
|
---|
[efcb393] | 241 | But the compiler itself uses an internal library implementing complex
|
---|
[5620622] | 242 | subroutines for functions not available in the assembler instruction set. This
|
---|
| 243 | internal library is named libgcc, and it must be linked to the glibc
|
---|
[efcb393] | 244 | library to be fully functional! Furthermore, the standard library for
|
---|
[5620622] | 245 | C++ (libstdc++) must also be linked with glibc. The solution to this
|
---|
| 246 | chicken and egg problem is first to build a degraded cc1-based libgcc,
|
---|
| 247 | lacking some functionalities such as threads and exception handling, and then
|
---|
| 248 | to build glibc using this degraded compiler (glibc itself is not
|
---|
| 249 | degraded), and also to build libstdc++. This last library will lack some of the
|
---|
| 250 | functionality of libgcc.</para>
|
---|
| 251 |
|
---|
| 252 | <para>This is not the end of the story: the upshot of the preceding
|
---|
[efcb393] | 253 | paragraph is that cc1 is unable to build a fully functional libstdc++, but
|
---|
| 254 | this is the only compiler available for building the C/C++ libraries
|
---|
| 255 | during stage 2! Of course, the compiler built during stage 2, cc-lfs,
|
---|
[79524a0] | 256 | would be able to build those libraries, but (1) the build system of
|
---|
[5620622] | 257 | gcc does not know that it is usable on pc, and (2) using it on pc
|
---|
| 258 | would create a risk of linking to the pc libraries, since cc-lfs is a native
|
---|
[543c94c] | 259 | compiler. So we have to re-build libstdc++ later as a part of
|
---|
| 260 | gcc stage 2.</para>
|
---|
| 261 |
|
---|
| 262 | <para>In &ch-final; (or <quote>stage 3</quote>), all packages needed for
|
---|
| 263 | the LFS system are built. Even if a package is already installed into
|
---|
| 264 | the LFS system in a previous chapter, we still rebuild the package
|
---|
| 265 | unless we are completely sure it's unnecessary. The main reason for
|
---|
| 266 | rebuilding these packages is to settle them down: if we reinstall a LFS
|
---|
| 267 | package on a complete LFS system, the installed content of the package
|
---|
| 268 | should be same as the content of the same package installed in
|
---|
| 269 | &ch-final;. The temporary packages installed in &ch-tmp-cross; or
|
---|
[b6d3512] | 270 | &ch-tmp-chroot; cannot satisfy this expectation because some of them
|
---|
[543c94c] | 271 | are built without optional dependencies installed, and autoconf cannot
|
---|
| 272 | perform some feature checks in &ch-tmp-cross; because of cross
|
---|
| 273 | compilation, causing the temporary packages to lack optional features
|
---|
| 274 | or use suboptimal code routines. Additionally, a minor reason for
|
---|
| 275 | rebuilding the packages is allowing to run the testsuite.</para>
|
---|
[efcb393] | 276 |
|
---|
| 277 | </sect2>
|
---|
| 278 |
|
---|
| 279 | <sect2 id="other-details">
|
---|
| 280 |
|
---|
| 281 | <title>Other procedural details</title>
|
---|
| 282 |
|
---|
| 283 | <para>The cross-compiler will be installed in a separate <filename
|
---|
| 284 | class="directory">$LFS/tools</filename> directory, since it will not
|
---|
| 285 | be part of the final system.</para>
|
---|
| 286 |
|
---|
| 287 | <para>Binutils is installed first because the <command>configure</command>
|
---|
[5620622] | 288 | runs of both gcc and glibc perform various feature tests on the assembler
|
---|
[efcb393] | 289 | and linker to determine which software features to enable or disable. This
|
---|
[5620622] | 290 | is more important than one might realize at first. An incorrectly configured
|
---|
| 291 | gcc or glibc can result in a subtly broken toolchain, where the impact of
|
---|
[efcb393] | 292 | such breakage might not show up until near the end of the build of an
|
---|
| 293 | entire distribution. A test suite failure will usually highlight this error
|
---|
| 294 | before too much additional work is performed.</para>
|
---|
| 295 |
|
---|
| 296 | <para>Binutils installs its assembler and linker in two locations,
|
---|
| 297 | <filename class="directory">$LFS/tools/bin</filename> and <filename
|
---|
| 298 | class="directory">$LFS/tools/$LFS_TGT/bin</filename>. The tools in one
|
---|
| 299 | location are hard linked to the other. An important facet of the linker is
|
---|
| 300 | its library search order. Detailed information can be obtained from
|
---|
| 301 | <command>ld</command> by passing it the <parameter>--verbose</parameter>
|
---|
| 302 | flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command>
|
---|
| 303 | will illustrate the current search paths and their order. It shows which
|
---|
| 304 | files are linked by <command>ld</command> by compiling a dummy program and
|
---|
| 305 | passing the <parameter>--verbose</parameter> switch to the linker. For
|
---|
| 306 | example,
|
---|
| 307 | <command>$LFS_TGT-gcc dummy.c -Wl,--verbose 2>&1 | grep succeeded</command>
|
---|
| 308 | will show all the files successfully opened during the linking.</para>
|
---|
| 309 |
|
---|
[5620622] | 310 | <para>The next package installed is gcc. An example of what can be
|
---|
[efcb393] | 311 | seen during its run of <command>configure</command> is:</para>
|
---|
| 312 |
|
---|
| 313 | <screen><computeroutput>checking what assembler to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/as
|
---|
| 314 | checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</computeroutput></screen>
|
---|
| 315 |
|
---|
| 316 | <para>This is important for the reasons mentioned above. It also
|
---|
[5620622] | 317 | demonstrates that gcc's configure script does not search the PATH
|
---|
[efcb393] | 318 | directories to find which tools to use. However, during the actual
|
---|
| 319 | operation of <command>gcc</command> itself, the same search paths are not
|
---|
| 320 | necessarily used. To find out which standard linker <command>gcc</command>
|
---|
| 321 | will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>.</para>
|
---|
| 322 |
|
---|
| 323 | <para>Detailed information can be obtained from <command>gcc</command> by
|
---|
| 324 | passing it the <parameter>-v</parameter> command line option while compiling
|
---|
| 325 | a dummy program. For example, <command>gcc -v dummy.c</command> will show
|
---|
| 326 | detailed information about the preprocessor, compilation, and assembly
|
---|
| 327 | stages, including <command>gcc</command>'s included search paths and their
|
---|
| 328 | order.</para>
|
---|
| 329 |
|
---|
| 330 | <para>Next installed are sanitized Linux API headers. These allow the
|
---|
[5620622] | 331 | standard C library (glibc) to interface with features that the Linux
|
---|
[efcb393] | 332 | kernel will provide.</para>
|
---|
| 333 |
|
---|
[5620622] | 334 | <para>The next package installed is glibc. The most important
|
---|
| 335 | considerations for building glibc are the compiler, binary tools, and
|
---|
| 336 | kernel headers. The compiler is generally not an issue since glibc will
|
---|
[efcb393] | 337 | always use the compiler relating to the <parameter>--host</parameter>
|
---|
| 338 | parameter passed to its configure script; e.g. in our case, the compiler
|
---|
| 339 | will be <command>$LFS_TGT-gcc</command>. The binary tools and kernel
|
---|
[7e62bbc] | 340 | headers can be a bit more complicated. Therefore, we take no risks and use
|
---|
[efcb393] | 341 | the available configure switches to enforce the correct selections. After
|
---|
| 342 | the run of <command>configure</command>, check the contents of the
|
---|
| 343 | <filename>config.make</filename> file in the <filename
|
---|
| 344 | class="directory">build</filename> directory for all important details.
|
---|
| 345 | Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with
|
---|
| 346 | <envar>$LFS_TGT</envar> expanded) to control which binary tools are used
|
---|
| 347 | and the use of the <parameter>-nostdinc</parameter> and
|
---|
| 348 | <parameter>-isystem</parameter> flags to control the compiler's include
|
---|
[5620622] | 349 | search path. These items highlight an important aspect of the glibc
|
---|
[efcb393] | 350 | package—it is very self-sufficient in terms of its build machinery
|
---|
| 351 | and generally does not rely on toolchain defaults.</para>
|
---|
| 352 |
|
---|
[5620622] | 353 | <para>As mentioned above, the standard C++ library is compiled next, followed in
|
---|
[ea9263c] | 354 | <xref linkend="chapter-temporary-tools"/> by other programs that need
|
---|
| 355 | to be cross compiled for breaking circular dependencies at build time.
|
---|
| 356 | The install step of all those packages uses the
|
---|
[5620622] | 357 | <envar>DESTDIR</envar> variable to force installation
|
---|
| 358 | in the LFS filesystem.</para>
|
---|
[79524a0] | 359 |
|
---|
[c68e018] | 360 | <para>At the end of <xref linkend="chapter-temporary-tools"/> the native
|
---|
[5620622] | 361 | LFS compiler is installed. First binutils-pass2 is built,
|
---|
| 362 | in the same <envar>DESTDIR</envar> directory as the other programs,
|
---|
[891b48b] | 363 | then the second pass of gcc is constructed, omitting some
|
---|
| 364 | non-critical libraries. Due to some weird logic in gcc's
|
---|
[79524a0] | 365 | configure script, <envar>CC_FOR_TARGET</envar> ends up as
|
---|
[5620622] | 366 | <command>cc</command> when the host is the same as the target, but
|
---|
[79524a0] | 367 | different from the build system. This is why
|
---|
[5620622] | 368 | <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is declared explicitly
|
---|
| 369 | as one of the configuration options.</para>
|
---|
[efcb393] | 370 |
|
---|
| 371 | <para>Upon entering the chroot environment in <xref
|
---|
[891b48b] | 372 | linkend="chapter-chroot-temporary-tools"/>,
|
---|
| 373 | the temporary installations of programs needed for the proper
|
---|
[00e20bee] | 374 | operation of the toolchain are performed. From this point onwards, the
|
---|
[a665a20] | 375 | core toolchain is self-contained and self-hosted. In
|
---|
[784dc13] | 376 | <xref linkend="chapter-building-system"/>, final versions of all the
|
---|
[efcb393] | 377 | packages needed for a fully functional system are built, tested and
|
---|
| 378 | installed.</para>
|
---|
| 379 |
|
---|
| 380 | </sect2>
|
---|
[b28fd35] | 381 |
|
---|
[673b0d8] | 382 | </sect1>
|
---|