Since systemd 246, libsystemd apparently automagically links against libzstd. I had zstd installed on my build system already, but it didn't get installed on the target system with the systemd binpkg run-time dependencies, so systemd 246 systems fail to boot. Reproducible: Always Steps to Reproduce: 1. emerge -v sys-apps/systemd # with zstd installed already Actual Results: Run-time dependency libzstd found: YES 1.4.5 ... enabled features: PAM, libfdisk, IMA, SECCOMP, SMACK, xz, zstd, ... ... # build succeeds buildsystem $ objdump -x /usr/lib/systemd/libsystemd-shared-246.so | grep zstd NEEDED libzstd.so.1 # on the target system that just installs binpkgs /sbin/init: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 Expected Results: The system should boot. Add zstd to DEPEND and RDEPEND, or maybe define a USE flag to toggle the meson option to fix this.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4bf7b81548f70cbf7ce5ae377e85fd21ae259ce7 commit 4bf7b81548f70cbf7ce5ae377e85fd21ae259ce7 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2020-10-14 19:14:59 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2020-10-14 19:15:32 +0000 sys-apps/systemd: add zstd USE flag Closes: https://bugs.gentoo.org/749023 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd/{systemd-246-r1.ebuild => systemd-246-r2.ebuild} | 7 +++++-- sys-apps/systemd/systemd-9999.ebuild | 7 +++++-- 2 files changed, 10 insertions(+), 4 deletions(-)
