edi does not work out of the box on ubuntu

[jeanguyomarch]

After successfully building and installing edi (on Ubuntu), it failed to startup because of the loader not finding libedi.so.

$ meson -Dlibclang-headerdir=/usr/lib/llvm-4.0/include/ -Dlibclang-libdir=/usr/lib/llvm-4.0/lib/ . build
[ ... ]

$ ninja -C build
[ ... ]

$ sudo ninja -C install
ninja: Entering directory `build'
[0/1] Installing files.
Installing src/lib/libedi.so.0.6.99 to /usr/local/lib/x86_64-linux-gnu/libedi.so.0.6.99
Installing src/bin/edi to /usr/local/bin/edi
Installing src/bin/edi_scm to /usr/local/bin/edi_scm
Installing src/bin/edi_build to /usr/local/bin/edi_build
Installing data/extra/templates/eflproject.tar.gz to /usr/local/share/edi/templates/skeletons/eflproject.tar.gz
Installing data/extra/templates/eflproject_python.tar.gz to /usr/local/share/edi/templates/skeletons/eflproject_python.tar.gz
Installing data/extra/templates/eflproject.edj to /usr/local/share/edi/templates/eflproject.edj
Installing data/extra/templates/eflproject_python.edj to /usr/local/share/edi/templates/eflproject_python.edj
Installing data/themes/white.edj to /usr/local/share/edi/themes/white.edj
Installing data/themes/solarized.edj to /usr/local/share/edi/themes/solarized.edj
Installing data/themes/solarized_dark.edj to /usr/local/share/edi/themes/solarized_dark.edj
Installing /home/jean/e/edi/build/doc/edi.1 to /usr/local/share/doc/edi
Installing /home/jean/e/edi/build/data/desktop/edi.desktop to /usr/local/share/applications
Installing /home/jean/e/edi/data/desktop/edi.png to /usr/local/share/icons/hicolor/256x256/apps
Installing /home/jean/e/edi/data/images/about.png to /usr/local/share/edi/images
Installing /home/jean/e/edi/data/images/welcome.png to /usr/local/share/edi/images
Installing /home/jean/e/edi/AUTHORS to /usr/local/share/info/edi
Running custom install script '/usr/bin/python3 /usr/share/meson/meson --internal gettext install --subdir=po --localedir=share/locale --pkgname=edi'
Running custom install script '/home/jean/e/edi/data/extra/templates/../../../scripts/world_read.sh /usr/local/share/edi/templates/eflproject.edj'
Running custom install script '/home/jean/e/edi/data/extra/templates/../../../scripts/world_read.sh /usr/local/share/edi/templates/eflproject_python.edj'
Running custom install script '/home/jean/e/edi/data/themes/../../scripts/world_read.sh /usr/local/share/edi/themes/white.edj'
Running custom install script '/home/jean/e/edi/data/themes/../../scripts/world_read.sh /usr/local/share/edi/themes/solarized.edj'
Running custom install script '/home/jean/e/edi/data/themes/../../scripts/world_read.sh /usr/local/share/edi/themes/solarized_dark.edj'

$ sudo ldconfig

$ edi                                                                                                                                                                                                                  
edi: error while loading shared libraries: libedi.so.0: cannot open shared object file: No such file or directory

It is annoying that meson does install the lib in that place. By default ubuntu (and many distros) adds support in ld.so.conf* so /usr/local/lib is indexed by ldconfig, but not /usr/local/lib/x86_64-linux-gnu/. If it is not possible to configure meson to install the library in the prefix, instead of adding a toolchain level of indirection, maybe this should be documented somewhere.

Thanks.

[andydotxyz]

Could this be the same as mesonbuild/meson#2535 ?
i.e. do you have the prefix set somehow?

[haxworx]

Yeh Debian installs libclang to a unusual prefix and the path isn't known by ldconfig.

[andydotxyz]

@jeanguyomarch any thoughts on this? It's the last ticket holding up the 0.7 release but I don't know if there is anything we can sensibly do about it?...

[haxworx]

I think the best solution would be to add some small documentation highlighting the issue. Simple solution locally is to add the path LD_LIBRARY_PATH or globally in /etc/ld.so.conf.d/*

…

On Thu, Sep 6, 2018 at 8:52 AM Andrew Williams ***@***.***> wrote: @jeanguyomarch <https://github.com/jeanguyomarch> any thoughts on this? It's the last ticket holding up the 0.7 release but I don't know if there is anything we can sensibly do about it?... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHHOVfqnFkhcgOFyisi_7jEYT3tRLromks5uYNQugaJpZM4RMsFx> .