mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-19 11:49:20 +01:00
Automatic merge of trunk into multilib
This commit is contained in:
commit
3a303528e6
@ -51,10 +51,21 @@
|
|||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>If Glibc needs to be upgraded to a newer version, (e.g. from
|
<para>If Linux kernel needs to be upgraded (for example, from
|
||||||
glibc-2.31 to glibc-2.32), it is safer to rebuild LFS. Though you
|
5.10.17 to 5.10.18 or 5.11.1), nothing else need to be rebuilt.
|
||||||
<emphasis>may</emphasis> be able to rebuild all the packages in their
|
The system will keep working fine thanks to the well-defined border
|
||||||
dependency order, we do not recommend it. </para>
|
between kernel and userspace. Specifically, Linux API headers
|
||||||
|
need not to be (and should not be, see the next item) upgraded
|
||||||
|
alongside the kernel. You'll need to reboot your system to use the
|
||||||
|
upgraded kernel.</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>If Linux API headers or Glibc needs to be upgraded to a newer
|
||||||
|
version, (e.g. from glibc-2.31 to glibc-2.32), it is safer to
|
||||||
|
rebuild LFS. Though you <emphasis>may</emphasis> be able to rebuild
|
||||||
|
all the packages in their dependency order, we do not recommend
|
||||||
|
it. </para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem> <para>If a package containing a shared library is updated, and
|
<listitem> <para>If a package containing a shared library is updated, and
|
||||||
|
Loading…
Reference in New Issue
Block a user