[Octave-bug-tracker] [bug #39065] libjvm detection on 64 bit systems for java package

[Philip Nienhuis]

Follow-up Comment #1, bug #39065 (project octave):

Have you tried this patch in a "fixed" Java package, including installation?

AFAIK the following happens during Java pkg installation:

Already during install (rather: configure) time the JVM needs to be found.
__java__.cc will be compiled into __java__.oct and isn't available during
configure & first stages of installation. So this patch doesn't help at that
stage.

I've added a file preinstall.m to the 1.2.9 Java package to help users find &
set all prerequisites for installation of the Java package. This file
preinstall.m will also have to be patched to detect the JVM in the .../server
directory.

All this patching (+ a new java pkg release) can just be avoided by adding a
simple symlink in ..../client pointing to .../server/libjvm.so, as outlined on
the wiki.
Your patch would only help those users that aren't allowed (because of e.g.,
system policies) to add this symlink.

In core octave there's already a configure flag for setting the JVM location
(but I don't know if it has ever been tested - I've got no 64-bit Linux yet).

All in all I wonder if patching the Java package + releasing a new one is
really worth the trouble.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39065>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/