Closed cacheguard closed 1 year ago
Is it possible to reproduce the same issue with meson and ninja? Nowadays./configure and make are simple wrapper of them.
Hi Yuwata,
Thank you for your post and sorry for our delayed response. We don't know meson and ninja (very funny names). But according to the output of the ./configure and make commands given above, it seems that ./configure launch "ninja -C build" and make execute ""meson build. If you think that we should use other options with those funny commands, please advise us.
All the Best, CG
Hi Yuwata,
Thank you for your post and sorry for our delayed response. We don't know meson and ninja (very funny names). But according to the output of the ./configure and make commands given above, it seems that ./configure launch "ninja -C build" and make execute ""meson build. If you think that we should use other options with those funny commands, please advise us.
All the Best, CG
Do you have any image/container of the distro in question by any chance? It would make tracking down the issue much easier.
The configure
script and the Makefile
are just thing wrappers around meson setup build
and ninja -C build
. So the fact that they were used is not really important, and as the pasted output shows, both meson
and ninja
were invoked as expected.
The relevant error is:
/usr/src/systemd-253/build/systemd: error while loading shared libraries: libsystemd-core-253.so: cannot open shared object file: No such file or directory
That is strange. Try to invoke /usr/src/systemd-253/build/systemd --version
and figure out why this doesn't work. I'm pretty sure that it's something special in your environment.
I'll close the bug. I'm fairly certain that this is an operator error or something specific to your system. Feel free to post additional info here, people should reply.
/usr/src/systemd-253/build/systemd: error while loading shared libraries: libsystemd-core-253.so: cannot open shared object file: No such file or directory
As build/systemd
uses $ORIGIN
in its RPATH
, the most likely reason for this error is that /proc
is not mounted in the build environment.
Ah, that could be it. I was thinking that rpath must be broken somehow, and this would explain how.
Thanks a lot for all responses.
The root cause was actually /proc. We normally compile all sources in a chroot jail without mounting /proc. Mounting /proc has unblocked the build process.
Without mounting /proc :
/usr/src/systemd-253/build/systemd --version
/usr/src/systemd-253/build/systemd: error while loading shared libraries: libsystemd-core-253.so: cannot open shared object file: No such file or directory
After having /proc mounted:
/usr/src/systemd-253/build/systemd --version
systemd 253 (253)
+PAM -AUDIT -SELINUX -APPARMOR +IMA +SMACK -SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL -ELFUTILS -FIDO2 -IDN2 -IDN +IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +TPM2 +BZIP2 -LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified
All the Best CG
I'm puzzled on this. I have a server that I just upgraded from Debian 11 to Debian 12. It has libvirtd. The only particular thing is that it uses the ZFS module.
I saw the same error during the upgrade process (and got a bit nervous), each time the module is compiled/removed when /etc/kernel/postrm.d/zz-update-grub is running (it appears 2 times in the lines below):
(Reading database ... 229515 files and directories currently installed.)
Removing linux-image-5.10.0-22-amd64 (5.10.178-3) ...
/etc/kernel/prerm.d/dkms:
dkms: removing: zfs 2.0.3 (5.10.0-22-amd64) (x86_64)
-------- Uninstall Beginning --------
Module: zfs
Version: 2.0.3
Kernel: 5.10.0-22-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
zavl.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
znvpair.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zunicode.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zcommon.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zfs.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
icp.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zlua.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
spl.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zzstd.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-22-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod....
DKMS: uninstall completed.
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-22-amd64
/etc/kernel/postrm.d/zz-update-grub:
systemd-detect-virt: error while loading shared libraries: libsystemd-shared-252.so: cannot open shared object file: No such file or directory
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-25-amd64
Found initrd image: /boot/initrd.img-5.10.0-25-amd64
Found linux image: /boot/vmlinuz-5.10.0-23-amd64
Found initrd image: /boot/initrd.img-5.10.0-23-amd64
Found linux image: /boot/vmlinuz-5.10.0-21-amd64
Found initrd image: /boot/initrd.img-5.10.0-21-amd64
done
Removing linux-image-5.10.0-21-amd64 (5.10.162-1) ...
/etc/kernel/prerm.d/dkms:
dkms: removing: zfs 2.0.3 (5.10.0-21-amd64) (x86_64)
-------- Uninstall Beginning --------
Module: zfs
Version: 2.0.3
Kernel: 5.10.0-21-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
zavl.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
znvpair.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zunicode.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zcommon.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zfs.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
icp.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zlua.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
spl.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
zzstd.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-21-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod....
DKMS: uninstall completed.
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-21-amd64
/etc/kernel/postrm.d/zz-update-grub:
systemd-detect-virt: error while loading shared libraries: libsystemd-shared-252.so: cannot open shared object file: No such file or directory
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-25-amd64
Found initrd image: /boot/initrd.img-5.10.0-25-amd64
Found linux image: /boot/vmlinuz-5.10.0-23-amd64
Found initrd image: /boot/initrd.img-5.10.0-23-amd64
done
@appzer0 please do not hijack unrelated bug reports. Also, plesae contact your distro for help, primarily.
Hey.
When testing the fixes in #30074, I just stumbled over the same issue (I've built systemd in a chroot, and had’t bind mounted /proc
... and seems the tests may even need further special filesystems).
Maybe it would help non-familiar people if systemd’s build system could just error out if it detects any necessary filesystems not being mounted?
Cheers, Chris.
systemd version the issue has been seen with
253
Used distribution
LFS
Linux kernel version used
4.19.288
CPU architectures issue was seen on
x86_64
Component
other
Expected behaviour you didn't see
make success
Unexpected behaviour you saw
Hi,
We are trying to compile and install systemd from scratch on a an LFS based Linux system. The command "make" can't finish the compilation job and produces the following errors (almost at the latest stage)
We executed the "./configure" command before and the result was as follows;
Any idea?
Thanks in advance, CG
Steps to reproduce the problem
./configure make
Additional program output to the terminal or log subsystem illustrating the issue
No response