Re: AppStream fails to configure if systemd is not explicitly set to false.
"Xi Ruoyao" ([email protected] via blfs-dev Mailing List) <[email protected]> Thu, 18 Dec 2025 12:18:06 +0800
| Newsgroups | gmane.linux.lfs.beyond.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 2025-12-16 at 11:52 -0600, Douglas R. Reno wrote: > On 12/16/25 11:42 AM, Bruce Dubbs ([email protected] via blfs-dev > Mailing List) wrote: > > On 12/16/25 5:30 AM, "Antonis" ([email protected] via > > blfs-dev Mailing List) wrote: > > > AppSteam fails to configure due to systemd automatically being set to > > > true. > > > > > > "Run-time dependency libsystemd found: NO (tried pkgconfig and cmake) > > > > > > ../meson.build:182:21: ERROR: Dependency "libsystemd" not found, tried > > > pkgconfig and cmake" > > > > > > Fixed by appending -D systemd=false > > > > I assume you are using the sysV book. > > > > Do you have all the required dependencies installed? I took a look at my > > log and the output of the meson command is: > > > > AppStream 1.1.1 > > > > User defined options > > apidocs : false > > buildtype: release > > prefix : /usr > > stemming : false > > > > I can't duplicate the problem. > > > > -- Bruce > > > Along those lines, I'd like to point out that elogind is listed as a > required dependency. That installs a symlink from libelogind.pc to > libsystemd.pc, so that should work as long as the user has installed > elogind... IMO we need to triage why this package wants libsystemd. If it needs libsystemd to communicate with logind, then it's a valid dependency but we still needs to demote elogind to recommended as it can be disabled. If it needs libsystemd for other purposes which don't work on a sysv- based system, we should just disable it and remove elogind from the dependency list. -- Xi Ruoyao <[email protected]> -- http://lists.linuxfromscratch.org/sympa/info/blfs-dev Unsubscribe: See the above information page