Hi, On Thu, 24 May 2012, Stefan Seyfried wrote:
There is, btw, a proper symlink in the java-jdk-gcj-compat package (or whatever that is named again ...).
It seems to be named java-1_5_0-gcj-compat, but as the pdftk is actually only usable with gcj and not with java, i'll probably have to hack it again to find (and use) rt.jar instead of libgcj.jar...
Isn't the libgcj the equivalent for java what libc.so.6 is for C code? We have a /lib64/libc.so.6 symlink so why can't we have a libgcj.jar symlink?
More like an equivalent of libc+libgcc(+libstdc++). It is even more version specific than those because the .jar can conceivably use bytecode that wasn't available in older compilers. Hence having just one .jar at a common location would theoretically prevent parallel installation of multiple gcc-java packages, which we want to support. But the strange thing is why pdftk needs to explicitely mention that libgcj.jar anywhere. The compiler gcj should always include it in normal compilations automatically (like gcc also adds the right path to libgcc). I know you said pdftk doesn't build when it isn't mentioned, but _that's_ what should be investigated. Could be either gcj doesn't add although it should, or that pdftk isn't using gcj properly, or the like. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org