FS#12142 - cinelerra misses libIlmImf.so.4

Attached to Project: Community Packages
Opened by orbisvicis (orbisvicis) - Sunday, 16 November 2008, 12:06 GMT
Last edited by Dan Griffiths (Ghost1227) - Sunday, 15 February 2009, 09:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
$ cinelerra
cinelerra: error while loading shared libraries: libIlmImf.so.4: cannot open shared object file: No such file or directory

Solution:
Rebuild cinelerra

Additional info:
* package version(s)
* config and/or log files etc.
community/cinelerra-cv 1061-3
extra/openexr 1.6.1-1

libIlmImf.* is provided by openexr

Steps to reproduce:
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Sunday, 15 February 2009, 09:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  After several failed attempts to contact swiergot, I have updated this package to use the updated git repositories. Should now be up to date and working fine.
Comment by Tomas M. (eldragon) - Sunday, 23 November 2008, 21:05 GMT
simply create symbolic links to the needed libraries
for the one in your report: do
# ln -s /usr/lib/libIlmImf.so /usr/lib/libIlmImf.so.4

then start cinelerra. it will complain about a different one, you will need to do a similar procedure until all needed libraries have been symlinked.
Comment by orbisvicis (orbisvicis) - Tuesday, 25 November 2008, 07:38 GMT
Isn't that considered "hackish" ?
Comment by Otto Allmendinger (OttoA) - Friday, 05 December 2008, 21:03 GMT
I had to link libIlmImf.so libImath.so libHalf.so libIex.so to .so.4 for cinelerra to work
Comment by Gavin Bisesi (Daenyth) - Saturday, 06 December 2008, 00:52 GMT
Symlinking like that is a bad idea. Recompiling the application against the newer library should be all that's needed. Just use abs and makepkg.
Comment by Otto Allmendinger (OttoA) - Saturday, 06 December 2008, 02:30 GMT
I know. Just wanted to document whats wrong with this package.
Comment by Mildred (mildred) - Thursday, 11 December 2008, 00:50 GMT
it should be fixed in the repositories, it just need recompiling.
Comment by Emanuele Rampichini (lele85) - Friday, 26 December 2008, 10:39 GMT
I confirm the bug. Recompiling works for me!

Loading...