From: Philip N. <pr....@hc...> - 2012-08-31 08:31:49
|
Terry Duell wrote: > On Thu, 30 Aug 2012 19:51:00 +1000, Philip Nienhuis > <pr....@hc...> wrote: > >> Martin Helm wrote: >>> Am 30.08.2012 08:28, schrieb Terry Duell: > [snip] >>> You are not alone with Fedora, the exactly same problem happens on all >>> openSUSE versions as well, I always have to create the appropriate >>> symlinks manually. I am not sure what the correct solution is (changing >>> the package policy for openjdk, creating the symbolic link when the >>> octave forge java package is installed, changing the source code of the >>> of java package). >> >> This always seems to be the case in 64 bit systems (AFAIK also on >> Windows 64b). >> If it gives some comfort: on Mac OSX it is worse. The Java libs and >> executables have been scattered all over the place there and often >> seem to be moved into other locations with new OSX version. > > Thanks for your responses, clearly this isn't just a problem that I have. > Going on a response I got back in Jan, it looks like it is a problem > confined to the 64 bit openjdk packages. Is that an upstream problem > i.e. something the openjdk maintainers can/should fix? Are you sure that on Sun Java this doesn't happen? Anyway it is not a bad idea to ask the openjdk maintainers why this decision was made. In the Octave-forge ML (http://sourceforge.net/mailarchive/forum.php?forum_name=octave-dev, it has a bit of a clumsy interface) there are a few more threads on this. Philip |