Summary: | dev-db/redis-6.0.9-r100 does not compile on a non-systemd gentoo | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jiri Pittner <jiri.pittner> |
Component: | Current packages | Assignee: | Sam James <sam> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | hydrapolic, ionen, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=767262 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jiri Pittner
2021-01-26 10:37:26 UTC
-DHAVE_LIBSYSTEMD Odd, my own build doesn't have that and builds fine without systemd. Seems the build system looks for "pkg-config --exists libsystemd && echo exists", does it say exists for you? Perhaps you have partial leftover files confusing the build system. Also please attach full build.log when reporting build failures, helps in figuring these things out. That aside, I guess this package could explicitly pass USE_SYSTEMD=yes/no env so it's not automagic. "pkg-config --exists libsystemd && echo exists" returns "exists" I have a libsystemd.pc, which is however not leftover, but from the elogind package installed on the system: lrwxrwxrwx 1 root root 13 Dec 17 20:44 /usr/lib/pkgconfig/libsystemd.pc -> libelogind.pc I have found a workaround: cd /usr/include; ln -s elogind/systemd systemd Then the include file is found and compilation successfull. I guess the build system should be more strict in distinguishing elogind from systemd, or elogind package shoud be fixed to provide symbolic link to /usr/include/systemd as well. Hm, elogind doesn't install a libsystemd.pc for me, only a libelogind.pc and no symlink. Maybe something odd to do with still being on a 17.0 profile? Unless something else I don't know about. (In reply to Ionen Wolkens from comment #3) > Hm, elogind doesn't install a libsystemd.pc for me, only a libelogind.pc and > no symlink. Maybe something odd to do with still being on a 17.0 profile? > Unless something else I don't know about. Please migrate to 17.1, ensure everything is clean, including nothing in /usr/local/*, and we can proceed from there. |