gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-02-08 15:23:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Automatic merge of trunk into multilib

Browse Source
This commit is contained in:
Thomas Trepl 2023-09-05 00:30:10 +02:00
commit 7d0d9ff80f
4 changed files with 29 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
appendices/dependencies.xml
View File

@ -437,6 +437,9 @@
<seglistitem>
<seg>
<ulink url='&github;/testing-cabal/subunit'>libsubunit</ulink>
and
<ulink url='http://cyberelk.net/tim/software/patchutils/'>
patchutils</ulink>
</seg>
</seglistitem>
</segmentedlist>

11
chapter01/changelog.xml
View File

@ -40,6 +40,17 @@
appropriate for the entry or if needed the entire day's listitem.
-->
<listitem>
<para>2023-09-04</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Move caution regarding building by mixing
different version of LFS to General Compilation Instructions. Fixes
<ulink url='&lfs-ticket-root;5338'>#5338</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>2023-09-02</para>
<itemizedlist>

29
chapter01/whatsnew.xml
View File

@ -11,36 +11,9 @@
<title>What's new since the last release</title>
<!--
This does not belong on this page. I don't want to address this now.
At first I thought it would go on another page, but nothing seems to fit.
Perhaps a new page - somthing like 'Upgrading an Existing LFS System'.
- Bruce 9/1/23
<caution>
<para>
During a development cycle of LFS, the instructions in the book is
often modified to adapt for a package update or take the advantage of
new features from updated packages. Mixing up the instructions of
different versions of the LFS book can cause subtle breakages. This
kind of issue is generally a result from reusing some script created
for a prior LFS release. Such a reuse is strongly discouraged. If
you are reusing scripts for a prior LFS release for any reason, you'll
need to be very careful to update the scripts to match current version
of the LFS book.
</para>
</caution>
<para>In the 12.0 release, <parameter>- -disable-fixincludes</parameter>
is set for GCC. It's a configure switch newly added in GCC 13.1 to
prevent GCC from <quote>fixing</quote> the system headers. Such a
<quote>fix</quote> is unnecessary for a modern Linux system and may cause
issues if a package is updated after installing GCC.</para>
<para>Here is a list of the packages updated since the previous
release of LFS.</para>
-->
<!--
Every package in the book is listed in the "Upgraded to:" section.
Comment/uncomment as needed. DO NOT delete any of these lines unless that

14
part3intro/generalinstructions.xml
View File

@ -11,6 +11,20 @@
<title>General Compilation Instructions</title>
<caution>
<para>
During a development cycle of LFS, the instructions in the book are
often modified to adapt for a package update or take the advantage of
new features from updated packages. Mixing up the instructions of
different versions of the LFS book can cause subtle breakages. This
kind of issue is generally a result from reusing some script created
for a prior LFS release. Such a reuse is strongly discouraged. If
you are reusing scripts for a prior LFS release for any reason, you'll
need to be very careful to update the scripts to match current version
of the LFS book.
</para>
</caution>
<para>Here are some things you should know about building each package:</para>
<itemizedlist>