Summary: | sys-fs/lvm2-2.03.14 - lvmlockd-core.c: fatal error: systemd/sd-daemon.h: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agk, robbat2, sandino |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 sys-fs:lvm2-2.03.14:20211105-231657.log temp.tar.bz2 emerge --info build log ebuild environment |
Description
Toralf Förster
2021-11-06 08:18:50 UTC
Created attachment 748944 [details]
emerge-info.txt
Created attachment 748947 [details]
emerge-history.txt
Created attachment 748950 [details]
environment
Created attachment 748953 [details]
etc.portage.tar.bz2
Created attachment 748956 [details]
logs.tar.bz2
Created attachment 748959 [details]
sys-fs:lvm2-2.03.14:20211105-231657.log
Created attachment 748962 [details]
temp.tar.bz2
Hello, I had the same problem, which is due to the use of flags: sanlock (-systemd); and I have solved it by doing a new ebuild, which contains the following lines, inside the src_prepare () section, before the 'eautoreconf' line: if ! use systemd ; then if use sanlock ; then sed -i -e "s:systemd/sd-daemon.h:elogind/systemd/sd-daemon.h:" daemons/lvmlockd/lvmlockd-core.c || die sed -i -e "s:libsystemd:libelogind:" daemons/lvmlockd/Makefile.in || die fi fi Good luck, I hope I have been of help to someone... PS: This happens because you don't like 'systemd' and refuse to have it installed on your machine... :) In daemons/lvmlockd/Makefile.in, USE_SD_NOTIFY is hard-coded to yes. It should probably be populated by configure instead. I have the same error on sys-fs/lvm2-2.03.14-r4 lvmlockd-core.c:35:10: fatal error: systemd/sd-daemon.h: No such file or directo ry 35 | #include <systemd/sd-daemon.h> | ^~~~~~~~~~~~~~~~~~~~~ emerge -pqv '=sys-fs/lvm2-2.03.14-r4::gentoo' [ebuild R ] sys-fs/lvm2-2.03.14-r4 USE="lvm readline sanlock* thin -lvm2cre ate-initrd (-selinux) -static -static-libs -systemd -udev" The same error also on 2.03.16-r1, 2.03.16-r2 and 2.03.17 Created attachment 835487 [details]
emerge --info
Created attachment 835489 [details]
build log
Created attachment 835491 [details]
ebuild environment
(In reply to Mike Gilbert from comment #9) > In daemons/lvmlockd/Makefile.in, USE_SD_NOTIFY is hard-coded to yes. It > should probably be populated by configure instead. Turning off the hardcoded USE_SD_NOTIFY=yes in daemons/lvmlockd/Makefile.in fixes the issue @@ -103,6 +103,10 @@ # Users without systemd get no auto-activation of any logical volume if ! use systemd ; then eapply "${FILESDIR}"/${PN}-2.03.14-dm_lvm_rules_no_systemd.patch + # Fix for Bug #822054 https://bugs.gentoo.org/822054 + if use sanlock ; then + sed -i -e "s:USE_SD_NOTIFY=yes:USE_SD_NOTIFY=no:" daemons/lvmlockd/Makefile.in || die + fi fi sed -i \ The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a05d2535777027dd8d43197b865768da4baf2126 commit a05d2535777027dd8d43197b865768da4baf2126 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2022-11-21 19:51:35 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2022-11-21 19:51:35 +0000 sys-fs/lvm2: fix build with USE="sanlock -systemd" Closes: https://bugs.gentoo.org/822054 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-fs/lvm2/lvm2-2.03.14-r4.ebuild | 1 + sys-fs/lvm2/lvm2-2.03.16-r2.ebuild | 1 + sys-fs/lvm2/lvm2-2.03.17.ebuild | 1 + 3 files changed, 3 insertions(+) |