libelektra: kdb fail to open backed (dlopen) libelektra-resolver.so, but is installed in /usr/lib/elektra instead of /usr/lib

open kdb without arguments

└───╼  kdb
Usage: kdb <command> [args]

kdb is a program to manage elektra's key database.
Please run a command with -H or --help as args to show a help text for
a specific command.

Known commands are:
Sorry, I have a severe problem, it seems like I am not installed correctly!
kdbOpen() failed with the info:
 Sorry, 1 warning was issued ;(
 Warning (#1):
        Description: could not load module, dlopen failed
        Ingroup: modules
        Module: dl
        At: /tmp/makepkg/elektra-git/src/elektra/src/libs/loader/dl.c:88
        Reason: of module: libelektra-resolver.so, because: libelektra-resolver.so: cannot open shared object file: No such file or directory
        Mountpoint: 
        Configfile: 
Sorry, the error (#40) occurred ;(
Description: failed to open default backend (see warnings for more information)
Ingroup: kdb
Module: 
At: /tmp/makepkg/elektra-git/src/elektra/src/libs/elektra/kdb.c:287
Reason: could not open default backend
Mountpoint: 
Configfile: 

Please report an issue on http://git.libelektra.org/issues

but the file exist in /usr/lib/elecktra

└───╼  locate libelektra-resolver.so
/usr/lib/elektra/libelektra-resolver.so

builded with:

  cd build
  cmake ../elektra \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DENABLE_TESTING=ON \
    -DBUILD_STATIC=OFF \
    -DTOOLS=ALL \
    -DPLUGINS='ALL;-experimental' \
    -DBINDINGS=ALL \
    -DLUA_EXECUTABLE=/usr/bin/lua \
    -DLUA_LIBRARY=/usr/lib/liblua.so \
    -DLUA_INCLUDE_DIR=/usr/include \
    -DTARGET_LUA_CMOD_FOLDER=lib/lua/5.3 \
    -DTARGET_LUA_LMOD_FOLDER=share/lua/5.3 \
    -DJAVA_INCLUDE_PATH="${JAVA_HOME}/include" \
    -DCMAKE_SKIP_INSTALL_RPATH=ON

  LC_ALL=C make

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 18 (14 by maintainers)

Commits related to this issue

Most upvoted comments

Thanks for pointing out. Reducing dependence on environment variables is well explained and understandable for elektra.

As a consequence of installing plugins into the main ldconfig paths, could elektra link it’s modules into bigger libraries sorted by their dependencies? That way they can still be separately packaged without cluttering the lib paths. E.g.: libelektra-modules.so libelektra-modules-augeas.so libelektra-modules-crypto.so libelektra-modules-dbus.so …