[arch-general] digikam doesn't find libIlmImf.so.6 after update to openexr
after openexr was updated yesterday from 1.7.0-2 -> 1.7.1-1, digikam failed to start with the following error: digikam: error while loading shared libraries: libIlmImf.so.6: cannot open shared object file: No such file or directory /usr/lib/libIlmImf.so.6 used to be provided by openexr; now it's called libIlmImf.so.7 instead. providing a symlink with the old name, pointing to the new one solved the problem. bug: https://bugs.archlinux.org/task/31923 -- phani.
On 13.10.2012 05:26, phanisvara wrote:
after openexr was updated yesterday from 1.7.0-2 -> 1.7.1-1, digikam failed to start with the following error:
digikam: error while loading shared libraries: libIlmImf.so.6: cannot open shared object file: No such file or directory
/usr/lib/libIlmImf.so.6 used to be provided by openexr; now it's called libIlmImf.so.7 instead. providing a symlink with the old name, pointing to the new one solved the problem.
Symlinks are NOT a solution, they are a very dirty hack and can blow up in your face. There is a reason why upstream developers change version numbers and this reason is that the new library is not compatible with the old one. Just rebuild the program using the library against the new version and you won't run into any trouble. -- Florian Pritz
On Saturday 13 Oct 2012 10:44:57 Florian Pritz wrote:
digikam: error while loading shared libraries: libIlmImf.so.6: cannot open shared object file: No such file or directory
/usr/lib/libIlmImf.so.6 used to be provided by openexr; now it's called libIlmImf.so.7 instead. providing a symlink with the old name, pointing to the new one solved the problem.
Symlinks are NOT a solution, they are a very dirty hack and can blow up in your face. There is a reason why upstream developers change version numbers and this reason is that the new library is not compatible with the old one.
Just rebuild the program using the library against the new version and you won't run into any trouble.
of course, but i expected this to be fixed soon, and it was: another update to gegl, kdebase, kdebase-runtime, kdelibs, and opencv solved the problem (not sure which one). in the meantime, the dirty hack let me use digikam, and it didn't blow up in my face. if it had, i'd have known whom to thank for, of course. if i wanted to compile everything myself i'd be running gentoo. -- phani.
participants (2)
-
Florian Pritz
-
phanisvara