| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Now perl-5.36 ships zlib-1.2.12, which is same as the book providing.
|
|
|
|
|
|
|
| |
Update to binutils-2.38.
Update to util-linux-2.38.1.
Update to Python3-3.10.6.
Update to glibc-2.36.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
-Dblkid is automatically detected, and other three options are meson
defaults.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
How did I copied "FAIL:" along with the test name? :(
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Reference: https://gcc.gnu.org/r12-1924
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The references already correctly decorated are not changed because "if
it's not broken don't fix it".
|
| | |
|
| |
| |
| |
| |
| |
| | |
* Add description for "wheel" command
* Explain why pip3 warning does not matter for us
* Format and typo fixes
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
meson, Markupsafe, and Jinja2
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
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 libcap-2.64.
Update to linux-5.17.3.
Update to gzip-1.12.
|
| |
|
|
|
|
| |
It now just untars into procps-ng-4.0.0 directory, as we expect.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|