<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - 0.22.0 does not find openjpeg-2.0.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=58906#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - 0.22.0 does not find openjpeg-2.0.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=58906">bug 58906</a> from <a class="email" href="mailto:ajohnson@redneon.com" title="Adrian Johnson <ajohnson@redneon.com>"> Adrian Johnson</a> <pre>(In reply to <a href="show_bug.cgi?id=58906#c32">comment #32</a>) > * Using configure and openjpeg2 in an non standard dir i get > > /home/tsdgeos/devel/poppler/glib/tmp-introspect13BDMh/.libs/lt-Poppler-0.18: > error while loading shared libraries: libopenjp2.so.7: cannot open shared > object file: No such file or directory I can reproduce this on Debian Testing if I install openjpeg2 in a directory that is not /usr/local or the directory I install poppler into. This problem is beyond my understanding of automake and libtool. From what I can find out on google this is not caused by anything in my patch but is caused by the Debian libtool which has been modified to disallow -rpath to non standard locations (<a href="https://wiki.debian.org/RpathIssue">https://wiki.debian.org/RpathIssue</a>). It seems to be this setting that is causing the problem: $ grep link_all_deplibs= libtool link_all_deplibs=no Compiling and installing an unpatched libtool fixes the problem. Other solutions include putting the openjpeg2 lib in LD_LIBRARY_PATH or installing it in the same prefix as poppler.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>