Changeset 8a8177f9 for chapter06/pkgmgt.xml
- Timestamp:
- 08/03/2014 04:37:17 PM (10 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- c26c46ba
- Parents:
- 0bf4dfe
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/pkgmgt.xml
r0bf4dfe r8a8177f9 52 52 <itemizedlist> 53 53 <listitem> 54 <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs 55 to be upgraded to a newer minor version, it is safer to rebuild LFS. 56 Though you <emphasis>may</emphasis> be able to get by rebuilding all 57 the packages in their dependency order, we do not recommend it. For 58 example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer 59 to rebuild. For micro version updates, a simple reinstallation usually 60 works, but is not guaranteed. For example, upgrading from glibc-2.3.4 61 to glibc-2.3.5 will not usually cause any problems.</para> 54 <para>If Glibc needs to be upgraded to a newer version, (e.g. from 55 glibc-2.19 to glibc-2.20, it is safer to rebuild LFS. Though you 56 <emphasis>may</emphasis> be able to rebuild all the packages in their 57 dependency order, we do not recommend it. </para> 62 58 </listitem> 63 59
Note:
See TracChangeset
for help on using the changeset viewer.