Problems with elogind, BLFS >= 9.1
by ordealbyfire83 from LinuxQuestions.org on (#5B362)
Regarding elogind there are these further installation instructions:
Code:ln -sfv libelogind.pc /usr/lib/pkgconfig/libsystemd.pc &&
ln -sfvn elogind /usr/include/systemdwith the explanation Quote:
What "software packages," precisely, need these symlinks? My experience here is showing me that a lot of packages are building a lot of systemd baggage that can't be found at runtime, and that's not good.
For example, consider the 'configure' output for PulseAudio as it is written in this book. It will use systemd-journald (obviously not present), etc.
I have tried building Mate desktop 1.24 on BLFS-9.1 and it is fundamentally broken beyond repair because of things like this. (Meaning: compilation succeeds as expected, but packages either will not run, or will throw infinite warnings until you terminate them.) Older versions worked flawlessly with non-elogind schemes. Mate surely supports elogind and I have adjusted all available 'configure' options accordingly, but these symlinks make some packages think systemd is present, and others not.
I hope somebody can look into this, because anything not in the BLFS book is totally broken because of stuff like this.
Code:ln -sfv libelogind.pc /usr/lib/pkgconfig/libsystemd.pc &&
ln -sfvn elogind /usr/include/systemdwith the explanation Quote:
| These commands install symlinks so that software packages find systemd compatible library and headers. |
For example, consider the 'configure' output for PulseAudio as it is written in this book. It will use systemd-journald (obviously not present), etc.
I have tried building Mate desktop 1.24 on BLFS-9.1 and it is fundamentally broken beyond repair because of things like this. (Meaning: compilation succeeds as expected, but packages either will not run, or will throw infinite warnings until you terminate them.) Older versions worked flawlessly with non-elogind schemes. Mate surely supports elogind and I have adjusted all available 'configure' options accordingly, but these symlinks make some packages think systemd is present, and others not.
I hope somebody can look into this, because anything not in the BLFS book is totally broken because of stuff like this.