mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-18 19:29:21 +01:00
toolchaintechnotes: Update the paragraph describing ch05 glibc
We no longer pass CC="$LFS_TGT-gcc -nostdinc -isysroot" since cross-chap5.
This commit is contained in:
parent
7119cf2a83
commit
678acc1775
@ -359,20 +359,17 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
|
|||||||
|
|
||||||
<para>Next comes glibc. The most important
|
<para>Next comes glibc. The most important
|
||||||
considerations for building glibc are the compiler, binary tools, and
|
considerations for building glibc are the compiler, binary tools, and
|
||||||
kernel headers. The compiler is generally not an issue since glibc will
|
kernel headers. The compiler and binary tools are generally not an issue
|
||||||
always use the compiler relating to the <parameter>--host</parameter>
|
since glibc will always those relating to the <parameter>--host</parameter>
|
||||||
parameter passed to its configure script; e.g., in our case, the compiler
|
parameter passed to its configure script; e.g., in our case, the compiler
|
||||||
will be <command>$LFS_TGT-gcc</command>. The binary tools and kernel
|
will be <command>$LFS_TGT-gcc</command> and the <command>readelf</command>
|
||||||
headers can be a bit more complicated. Therefore, we take no risks and use
|
tool will be <command>$LFS_TGT-readelf</command>. The kernel headers can
|
||||||
the available configure switches to enforce the correct selections. After
|
be a bit more complicated. Therefore, we take no risks and use
|
||||||
|
the available configure switch to enforce the correct selection. After
|
||||||
the run of <command>configure</command>, check the contents of the
|
the run of <command>configure</command>, check the contents of the
|
||||||
<filename>config.make</filename> file in the <filename
|
<filename>config.make</filename> file in the <filename
|
||||||
class="directory">build</filename> directory for all important details.
|
class="directory">build</filename> directory for all important details.
|
||||||
Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with
|
These items highlight an important aspect of the glibc
|
||||||
<envar>$LFS_TGT</envar> expanded) to control which binary tools are used
|
|
||||||
and the use of the <parameter>-nostdinc</parameter> and
|
|
||||||
<parameter>-isystem</parameter> flags to control the compiler's include
|
|
||||||
search path. These items highlight an important aspect of the glibc
|
|
||||||
package—it is very self-sufficient in terms of its build machinery,
|
package—it is very self-sufficient in terms of its build machinery,
|
||||||
and generally does not rely on toolchain defaults.</para>
|
and generally does not rely on toolchain defaults.</para>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user