On 8/23/19 8:31 PM, Ken Moffat via blfs-dev wrote:
On Fri, Aug 23, 2019 at 02:49:15AM +0100, Ken Moffat via blfs-dev wrote:
With the book's current instructions, ModemManager (which appears to
now be _required_ for geoclue, but maybe I'm misunderstanding the
meson options for geoclue) fails to build:
checking for vapigen... yes
Package systemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `systemd.pc'
to the PKG_CONFIG_PATH environment variable
No package 'systemd' found
checking for GUDEV... yes
checking for LIBSYSTEMD... no
checking for LIBSYSTEMD_LOGIN... no
configure: error: libsystemd or libsystemd-login development headers are
required
There is an old patch from DJ to update configure.ac and
Makefile.in, but the Makefile.in part rejects. I've now managed to
build it using the following (based on gentoo) :
LIBSYSTEMD_LOGIN_CFLAGS=`pkg-config --cflags "libelogind"` \
LIBSYSTEMD_LOGIN_LIBS=`pkg-config --libs "libelogind"` \
./configure --prefix=/usr \
(etc).
I've no idea if it works, and I see that the build was not verbose -
but I don't really have a use for MM, or even for geoclue (unless it
turns out to be the magic bullet for epiphany), just trying to check
that things build.
ĸen
After running a verbose build, and a verbose DESTDIR install,
followed by ldd on all the libs in the DESTDIR, I think that for
the sysv book elogind is just a build dependency, i.e. it doesn't
actually link to it.
But I have no use for ModemManager, except that geoclue seems to
require it. Not sure if I should put this in the sysv book ?
ĸen
The primary reason why ModemManager needs elogind is so that it can gain
access to device nodes for manipulating GSM/3G/4G/ (upcoming) 5G modems.
It performs the same way that systemd-logind does in that case
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
