Hi, On Tue, Aug 24, 2010 at 08:50:13AM +0200, Stephan Bergmann wrote: > The static > NativeLibraryLoader.loadLibrary(PipeConnection.class.getClassLoader(), > "jpipe"); in class com.sun.star.lib.connections.pip.PipeConnection > within jurt.jar effectively depends on finding a jpipe dynamic library > (libjpipe.so on Linux) through the Class-Path in the jurt.jar > META-INF/MANIFEST.MF, "ridl.jar unoloader.jar ../../lib/ ../bin/".
Ah, OK. > This works in standard OOo installations, where the jpipe dynamic > library is found relative to jurt.jar within the URE installation either > in ../../lib (Unix) or ../bin (Windows). > > This fails if you either use a jurt.jar copied elsewhere, or the given > OOo installation does not preserve the above requirement. r...@frodo:~$ cd /usr/lib/ure/share/java/ r...@frodo:/usr/lib/ure/share/java$ ls -l ../../lib/libj libjava_uno libjuh.so libjvmfwk.so.3 libjava_uno.so libjuhx.so libjpipe.so libjvmaccessgcc3.so.3 r...@frodo:/usr/lib/ure/share/java$ ls -l ../../lib/libjpipe.so -rw-r--r-- 1 root root 9280 23. Aug 21:19 ../../lib/libjpipe.so But: r...@frodo:/usr/lib/ure/share/java$ ls -l jurt.jar lrwxrwxrwx 1 root root 31 23. Aug 21:58 jurt.jar -> ../../../../share/java/jurt.jar So the symlink is the problem? Grmpf. Why can't you for one time just handle symlinks correctly.... Grüße/Regards, René --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
