Issue with LD_LIBRARY_PATH

Alexander Larsson alexl at redhat.com
Tue Dec 4 07:36:59 UTC 2018


On Tue, Dec 4, 2018 at 4:49 AM Daniel Kasak <d.j.kasak.dk at gmail.com> wrote:
>
> I have an app that needs some libraries that are linked against some strange version of a lib ... it's a long story ... anyway the *official* advice from the vendor is to create a symbolic link pointing to whatever version of libcom_err I have, so:
>
> lrwxrwxrwx 1 dkasak dkasak       39 Dec  4 14:07 libcom_err.so.3 -> /usr/lib/x86_64-linux-gnu/libcom_err.so

The *.so files are development versions of the library only available
in the sdk. You need to point it at libcom_err.so.2, or whatever
version the runtime your app uses has.

Also, LD_LIBRARY_PATH is sometimes set by flatpak, so make sure you
override it by extending it, not replacing it:


More information about the Flatpak mailing list