There are periodically users reporting that the --with-sysroot option
does not exist in binutils and gcc. Add a note telling that not all
aoptions are visible at the top level of the tree, unless
--help=recursive is passed. Take --with-sysroot as an example, so
that users have everything to find it...
I still think this is obvious but it seems some people are surprised by
"unknown host" in chroot. Let's just note it before they propose a
change for every BLFS package of which the build process requires an
Internet connection.
Update to readline-8.3.
Update to perl-5.42.0.
Update to openssl-3.5.1.
Update to ninja-1.13.1.
Update to linux-6.15.6.
Update to gettext-0.25.1.
Update to e2fsprogs-1.47.3.
Update to bash-5.3.
Update to iana-etc-20250618.
Update to vim-9.1.1497.
Update to util-linux-2.41.1.
Update to shadow-4.18.0.
Update to pkgconf-2.5.1.
Update to ninja-1.13.0.
Update to linux-6.15.4.
Update to less-679.
Update to automake-1.18.1.
The problem is that TIC_PATH is nor honored anymore in chapter
6, so that tic from the host is used to create the terminfo
database in chapter 6. The problem is that old versions of
tic create symlinks in the database, while newer versions
create hardlinks. Since we use a DESTDIR install in chapter 8
(with a recent version of ncurses, so with hardlinks), and copy
it in place with cp -a, then it seems that copying hardlinks to
symlinks. If an old version of tic has been used in chapter 6,
this copies hardlinks to symlinks, which creates symlinks
pointing to themselves (cp bug?).
Anyway, the solution is to copy the auxilliary tic built
in chapter 6 to $LFS/tools/bin (suggestion by Xi Ruoyao).
Now, there is no need to set TIC_PATH or whatever because this
tic is in the PATH.
Bug first reported by Marcin Dulak. Analysis with the help of
Bruce Dubbs and Thomas Trepl.
Fixes https://wiki.linuxfromscratch.org/lfs/ticket/5744
Without it, in the final system
/usr/lib/python3.13/config-3.13-$triple/libpython3.13.a is a remnant
from chapter 7 instead of being absent, defeating our will to save
space.
Make this consistent with addinguser.
Applying chown to a symlink actually affects its target, and here the
targets are in $LFS/usr and already covered.
Update to iana-etc-20250519.
Update to vim-9.1.1418.
Update to kbd-2.8.0.
Update to systemd-257.6.
Update to setuptools-80.9.0.
Update to meson-1.8.1.
Update to automake-1.18.
Update to gcc-15.1.0.
Update build instructions to accomodate gcc-15.
Update to less-678.
Update to readline-8.3-rc1.
Update to bash-5.3-rc1.
Update to systemd-257.6.
Update to setuptools-80.9.0.
Update to meson-1.8.1.
Update to automake-1.18.
Add Python-3.13.3-security_fixes-1.patch
Add coreutils-9.7-upstream_fix-1.patch
Add perl-5.40.2-upstream_fix-1.patch
Someone is really insistant on "you cannot have any extra whitespace" so
the hack will just not work. Let's drop it and simply move the
--enable-kernel= switches to the last line.
Update to vim-9.1.1353.
Update to setuptools-80.0.1.
Update to packaging-25.0.
Update to meson-1.8.0.
Update to linux-6.14.4.
Update to iana-etc-20250407.
Update to gperf-3.3.
Update to elfutils-0.193.
