Rene Engelhard wrote:
Well, it *might* be the cause that OOo doesn't grok that classes/ is a
symlink.
Yes, a symlink does not work here. Much OOo Java code (residing in jar
files in program/classes) needs to find other OOo files (native
libraries etc.) and does so using NativeLibraryLoader
(jurt/com/sun/star/lib/util/NativeLibraryLoader.java:1.9).
NativeLibraryLoader effectively goes up the directory hierarchy one
level from program/classes to program to locate those files. That of
course breaks if program/classes is a symlink to somewhere else.
Much OOo code (Java and C++) is working in ways that will break if the
OOo installation structure is changed. This is often problematic, and
should overall be changed I think. However, it also implies that
whoever now fiddles with the OOo installation structure causes pain, not
only to those poor souls that happen to use the deviating installation,
but also to all community members who help to sort out the mess.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
