Am 24.05.2012 17:01, schrieb Michael Matz:
Hi,
On Thu, 24 May 2012, Stefan Seyfried wrote:
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++).
Ok, that enlightens the darkness a little bit.
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.
libgcj-devel pulls in the latest gcc-java, libgcj*devel etc. anyway, so the libgcj.jar symlink that's in there would point to the latest version of course.
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.
Yeah, but In this case I'm a dumb packager with no intention of debugging either pdftk or gcj (or even learn java or such). So I'll add another hack to the specfile every time a new gcc version comes out and be done with that :-) I'll leave the scientific approach to the scientists. Best regards, seife -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org