diff options
| author | Pierre Labastie <pieere@linuxfromscratch.org> | 2020-06-13 08:55:55 +0000 |
|---|---|---|
| committer | Pierre Labastie <pieere@linuxfromscratch.org> | 2020-06-13 08:55:55 +0000 |
| commit | 77d2cd8d437a6ba11e13ac0af109a887582e988b (patch) | |
| tree | 485cafd860184d7a0fd87eedf50bfb3747ba42c7 /chapter05 | |
| parent | ad15abd0c0eee1ed646e1de45a525c61d3508358 (diff) | |
- fix some gcc->GCC
- remove commented text in glibc (chap 5), and fix a directory location
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11934 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/gcc-pass1.xml | 2 | ||||
| -rw-r--r-- | chapter05/glibc.xml | 25 | ||||
| -rw-r--r-- | chapter05/toolchaintechnotes.xml | 2 |
3 files changed, 6 insertions, 23 deletions
diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index e2a13a003..0cd852ee6 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -193,7 +193,7 @@ cd build</userinput></screen> headers. Normally one of them, <filename>limits.h</filename>, would in turn include the corresponding system <filename>limits.h</filename> header, in this case, <filename>$LFS/usr/include/limits.h</filename>. However, at the - time of this build of gcc <filename>$LFS/usr/include/limits.h</filename> + time of this build of GCC <filename>$LFS/usr/include/limits.h</filename> does not exist, so the internal header that has just been installed is a partial, self-contained file and does not include the extended features of the system header. This is adequate for building glibc, but the full diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 6e14f0c7d..1b72b4e20 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -99,9 +99,10 @@ cd build</userinput></screen> <varlistentry> <term><parameter>--with-headers=$LFS/usr/include</parameter></term> <listitem> - <para>This tells Glibc to compile itself against the headers recently - installed to the usr/include directory, so that it knows exactly what - features the kernel has and can optimize itself accordingly.</para> + <para>This tells Glibc to compile itself against the headers + recently installed to the $LFS/usr/include directory, so that + it knows exactly what features the kernel has and can optimize + itself accordingly.</para> </listitem> </varlistentry> @@ -112,24 +113,6 @@ cd build</userinput></screen> of the default /lib64 on 64 bit machines.</para> </listitem> </varlistentry> -<!-- - <varlistentry> - <term><parameter>libc_cv_c_cleanup=yes</parameter></term> - <listitem> - <para>Similarly, we pass libc_cv_c_cleanup=yes through to the - <command>configure</command> script so that the test is skipped and C - cleanup handling support is configured.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><parameter>libc_cv_ctors_header=yes</parameter></term> - <listitem> - <para>Similarly, we pass libc_cv_ctors_header=yes through to the - <command>configure</command> script so that the test is skipped and - gcc constructor support is configured.</para> - </listitem> - </varlistentry>--> </variablelist> diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml index 9e582e345..1e7086aaf 100644 --- a/chapter05/toolchaintechnotes.xml +++ b/chapter05/toolchaintechnotes.xml @@ -227,7 +227,7 @@ this is the only compiler available for building the C/C++ libraries during stage 2! Of course, the compiler built during stage 2, cc-lfs, would be able to build those libraries, but (1) the build system of - gcc does not know that it is usable on pc, and (2) using it on pc + GCC does not know that it is usable on pc, and (2) using it on pc would be at risk of linking to the pc libraries, since cc-lfs is a native compiler. So we have to build libstdc++ later, in chroot.</para> |