From 9ae3d8ad311e538d55b0dc6cd4f17de7ba1dd35f Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Mon, 8 May 2023 19:10:33 +0800 Subject: whatsnew: Update for GCC 13.1 And let's discourage reusing scripts. --- chapter01/whatsnew.xml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) (limited to 'chapter01') diff --git a/chapter01/whatsnew.xml b/chapter01/whatsnew.xml index 174eb384e..8c2bfda05 100644 --- a/chapter01/whatsnew.xml +++ b/chapter01/whatsnew.xml @@ -11,13 +11,25 @@ What's new since the last release - In the 11.3 release, --enable-default-pie - and --enable-default-ssp are enabled for GCC. - These techniques can mitigate some malicious attacks, but they do not provide - perfect security. Note that some textbooks assume these options are - disabled, so that if you run examples from such a textbook on an LFS system, - you may need to disable PIE and SSP with the GCC options - -fno-pie -no-pie -fno-stack-protection. + + + 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. + + + + In the 11.4 release, --disable-fixincludes + is set for GCC. It's a configure switch newly added in GCC 13.1 to + prevent GCC from fixing the system headers. Such a + fix is unnecessary for a modern Linux system and may cause + issues if a package is updated after installing GCC. Here is a list of the packages updated since the previous release of LFS. -- cgit v1.2.3-54-g00ecf