mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-07-09 22:04:35 +01:00
Minor text clarification
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11115 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
d3e008f892
commit
9d6ddc4efb
@ -45,11 +45,14 @@
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>2016-08-22</para>
|
<para>2016-08-22</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
<listitem>
|
||||||
|
<para>[bdubbs] - Release LFS-7.10-rc1.</para>
|
||||||
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>[bdubbs] - Update to linux-4.7.2. Fixes
|
<para>[bdubbs] - Update to linux-4.7.2. Fixes
|
||||||
<ulink url="&lfs-ticket-root;3972">#3972</ulink>.</para>
|
<ulink url="&lfs-ticket-root;3972">#3972</ulink>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem revision="systemd">
|
<listitem revision="systemd">
|
||||||
<para>[bdubbs] - Update to dbus-1.10.10. Fixes
|
<para>[bdubbs] - Update to dbus-1.10.10. Fixes
|
||||||
<ulink url="&lfs-ticket-root;3967">#3967</ulink>.</para>
|
<ulink url="&lfs-ticket-root;3967">#3967</ulink>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -127,7 +127,7 @@ checking what linker to use... /tools/i686-lfs-linux-gnu/bin/ld</computeroutput>
|
|||||||
for building Glibc are the compiler, binary tools, and kernel headers. The
|
for building Glibc are the compiler, binary tools, and kernel headers. The
|
||||||
compiler is generally not an issue since Glibc will always use the compiler
|
compiler is generally not an issue since Glibc will always use the compiler
|
||||||
relating to the <parameter>--host</parameter> parameter passed to its
|
relating to the <parameter>--host</parameter> parameter passed to its
|
||||||
configure script, e.g. in our case,
|
configure script; e.g. in our case, the compiler will be
|
||||||
<command>i686-lfs-linux-gnu-gcc</command>. The binary tools and kernel
|
<command>i686-lfs-linux-gnu-gcc</command>. The binary tools and kernel
|
||||||
headers can be a bit more complicated. Therefore, take no risks and use the
|
headers can be a bit more complicated. Therefore, take no risks and use the
|
||||||
available configure switches to enforce the correct selections. After the run
|
available configure switches to enforce the correct selections. After the run
|
||||||
|
Loading…
Reference in New Issue
Block a user