The help of this options says:
"However, if you have a new compiler with ..., you may need to disable
this config option in order to successfully build the kernel."
As we are having state-of-art GCC-12, and Linux-5.18 release candidate
FTBFS with GCC-12 and CONFIG_WERROR=y [1], and <rant>the kernel developers
are making stupid and meaningless discussion instead of fixing the building
failure</rant> [2], I don't think enabling this option makes any sense
building LFS.
[1]:https://lkml.org/lkml/2022/4/14/1676
[2]:https://lkml.org/lkml/2022/4/21/254
The other stats have not changed significantly (usually only
+/- 0.1 SBU).
By the way, the changes for gcc-pass2 also include the change
from merging libstdc++-pass2 into gcc-pass2.
Change nobody/nogroup uid/git to 65534.
Update to meson-0.62.1.
Update to libpipeline-1.5.6.
Update to elfutils-0.187.
Update to Jinja2-3.1.2.
Update to vim-8.2.4814.
Update to sysvinit-3.03.
Update to linux-5.17.5.
Update to gcc-11.3.0.
Update to coreutils-9.1.
Update to bc-5.2.4.
In serveral places we use the pip3 command to install Python 3 programs
and modules for all users as root. This conflicts with the Python
developers' recommendation to build packages in a virtual environment as
a regular user. To this end, a multi-line warning is written when using
pip3 as the root user.
This change shows users how to avoid this warning.
Update to sysvinit-3.02.
Update to zlib-1.2.12.
Update to expat-2.4.8.
Update to Jinja2-3.1.1.
Update to Python-3.10.4.
Update to procps-ng-4.0.0.
Update to iproute2-5.17.0.
Update to meson-0.62.0.
Update to linux-5.17.1.
Update to util-linux-2.38.
Telling the user to override CFLAGS and CXXFLAGS may cause two problems:
1. We've added --with-gcc-arch=native, so the configure script will add
"-march=native" into CFLAGS. Then we've not really verified which
-march= value is the last one in the GCC command line and being really
used.
2. User may just export CFLAGS="-march=x86_64", without "-O2". This
will produce unoptimized binaries.
