| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Security Advisory to follow.
|
|
|
|
|
| |
Update to linux-5.18.14.
Update to libcap-2.65.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Update to meson-0.63.0.
Update to kmod-30.
Update to inetutils-2.3.
Update to linux-5.18.9.
Update to OpenSSL-3.0.5.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It works out of box with glibc-2.35. I think this issue is already
fixed at glibc side, by the commit:
commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82
Author: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue Sep 21 07:47:45 2021 -0700
regex: copy back from Gnulib
Copy regex-related files back from Gnulib, to fix a problem with
static checking of regex calls noted by Martin Sebor. This merges the
following changes:
* New macro __attribute_nonnull__ in misc/sys/cdefs.h, for use later
when copying other files back from Gnulib.
... ... (unrelated things trimmed)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Update to vim-9.0.0006.
Update to iana-etc-20220610.
Update to OpenSSL-3.0.4.
Update to kbd-2.5.1.
Update to linux-5.18.8.
Update to bc-5.3.3.
+
|
|
|
|
|
|
|
|
| |
Presently we let the build system generate static C++ bindings, and
then we remove them. Note that we could also prevent generating
any C++ binding, since nothing in LFS/BLFS use them, but it seems to
me that generating the shared ones is closer to what is done for
other packages.
|
| |
|
|
|
|
|
|
|
| |
They are deprecated since 2007, and the next grep release (3.8 or 4.0)
will print a warning if they are used.
Url: https://git.savannah.gnu.org/cgit/grep.git/commit/?id=a951562
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The c_rehash script, shipped by OpenSSL versions in current LFS trunk
and all previous LFS releases, is vulnerable to CVE-2022-2068. It's
fixed in 3.0.4, but OpenSSL 3.0.4 is completely broken on CPU models with
AVX-512 extension [1]. So we'd like to defer OpenSSL update and wait for
upstream consensus about "would 3.0.5 be released in urgency".
But, the upstream has announced that use of c_rehash is obsolete now [2].
So we can tell people not to use it.
[1]: https://github.com/openssl/openssl/issues/18625
[2]: https://www.openssl.org/news/secadv/20220621.txt
|
|
|
|
|
|
|
|
| |
Using readline can improve line editing feature of bc, but it's not
enabled by default.
As readline is already installed before bc, let's pick up this
improvement with no cost.
|
| |
|
|
|
|
|
|
| |
I've observed some failures building LFS on my old i3-3217U (at 1.8 GHz
with -j4), but forgot to update the book. Just got reminded by a
lfs-support post.
|
|
|
|
|
|
|
|
| |
It's irrational to force a sysv builder to download systemd, or vice
versa. But we cannot simply make wget-list specific for revision: IIRC
the wget-list file with all packages in either revision is used by some
scripts on rivendell. So we keep wget-list as is, and provide a new
wget-list-$(REV) file which only contains the packages for one revision.
|
|
|
|
|
|
|
|
|
| |
Update to python3-3.10.5.
Update to meson-0.62.2.
Update to kbd-2.5.0.
Update to file-5.42.
Update to linux-5.18.3.
Update to bc-5.3.1.
|
|
|
|
|
|
|
|
|
| |
BLFS no longer contains ConsoleKit, and ConsoleKit can be considered
dead now (the ConsoleKit2 fork has no action in the recent year).
In BLFS systemd (with PAM) or elogind provide a similar functionality.
I can see no reason to mention ConsoleKit in the book now.
|
|
|
|
|
|
|
| |
Update to iana-etc-20220524.
Update to iproute2-5.18.0.
Update to linux-5.18.1.
Update to perl-6.36.0.
|
|
|
|
|
|
|
|
|
|
| |
Q: Why not just move the note after the creation of root-level
directories?
A: Root-level directories may be already created as well: if a
root-level directory is a mount point it should have been created in
section "Mounting the New Partition".
Reported-by: Vladimir Pertsev <info@linuxfromscratch.ru>
|
|
|
|
| |
systemd-networkd won't be used for network configuration
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
-Dblkid is automatically detected, and other three options are meson
defaults.
|
| |
|
| |
|
| |
|
|
|
|
| |
What was I doing ?!
|
| |
|
|
|
|
|
|
| |
With the construct used in save_usrlib, if ld-linux-...dbg already
exists, it is stripped again and a file ld-linux-...dbg.dbg is
created. Prevent this by not listing files ending in "g".
|
|
|
|
|
| |
Seems to be fixed upstream, but adding a patch for just a test
is overkill IMO.
|
|
|
|
|
| |
Update to linux-5.17.7.
Update to psmisc-23.5.
|
| |
|
| |
|
|
|
|
| |
How did I copied "FAIL:" along with the test name? :(
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
According to upstream, this issue is fixed:
https://github.com/util-linux/util-linux/issues/1635.
Also tested by Pierre and me.
|
| |
|
|
|
|
|
|
|
| |
The analyzer tests fixed at https://gcc.gnu.org/r12-7119.
The PR100400 status is discussed in the thread started with
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/593931.html.
|
|
|
|
|
| |
libstdc++.so.6.0.29 to 6.0.30. The versions of other GCC runtime libraries
are not bumped.
|