Changeset 1ec60f1d
- Timestamp:
- 09/04/2023 08:08:43 PM (13 months ago)
- Branches:
- 12.1, 12.1-rc1, 12.2, 12.2-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/update-glibc
- Children:
- 7d0d9ff, b1b9182
- Parents:
- 26c031a
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r26c031a r1ec60f1d 40 40 appropriate for the entry or if needed the entire day's listitem. 41 41 --> 42 43 <listitem> 44 <para>2023-09-04</para> 45 <itemizedlist> 46 <listitem> 47 <para>[bdubbs] - Move caution regarding building by mixing 48 different version of LFS to General Compilation Instructions. Fixes 49 <ulink url='&lfs-ticket-root;5338'>#5338</ulink>.</para> 50 </listitem> 51 </itemizedlist> 52 </listitem> 42 53 43 54 <listitem> -
chapter01/whatsnew.xml
r26c031a r1ec60f1d 12 12 <title>What's new since the last release</title> 13 13 14 <!--15 16 This does not belong on this page. I don't want to address this now.17 At first I thought it would go on another page, but nothing seems to fit.18 Perhaps a new page - somthing like 'Upgrading an Existing LFS System'.19 - Bruce 9/1/2320 21 <caution>22 <para>23 During a development cycle of LFS, the instructions in the book is24 often modified to adapt for a package update or take the advantage of25 new features from updated packages. Mixing up the instructions of26 different versions of the LFS book can cause subtle breakages. This27 kind of issue is generally a result from reusing some script created28 for a prior LFS release. Such a reuse is strongly discouraged. If29 you are reusing scripts for a prior LFS release for any reason, you'll30 need to be very careful to update the scripts to match current version31 of the LFS book.32 </para>33 </caution>34 35 <para>In the 12.0 release, <parameter>- -disable-fixincludes</parameter>36 is set for GCC. It's a configure switch newly added in GCC 13.1 to37 prevent GCC from <quote>fixing</quote> the system headers. Such a38 <quote>fix</quote> is unnecessary for a modern Linux system and may cause39 issues if a package is updated after installing GCC.</para>40 41 14 <para>Here is a list of the packages updated since the previous 42 15 release of LFS.</para> 43 --> 16 44 17 <!-- 45 18 Every package in the book is listed in the "Upgraded to:" section. -
part3intro/generalinstructions.xml
r26c031a r1ec60f1d 11 11 12 12 <title>General Compilation Instructions</title> 13 14 <caution> 15 <para> 16 During a development cycle of LFS, the instructions in the book are 17 often modified to adapt for a package update or take the advantage of 18 new features from updated packages. Mixing up the instructions of 19 different versions of the LFS book can cause subtle breakages. This 20 kind of issue is generally a result from reusing some script created 21 for a prior LFS release. Such a reuse is strongly discouraged. If 22 you are reusing scripts for a prior LFS release for any reason, you'll 23 need to be very careful to update the scripts to match current version 24 of the LFS book. 25 </para> 26 </caution> 13 27 14 28 <para>Here are some things you should know about building each package:</para>
Note:
See TracChangeset
for help on using the changeset viewer.