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

[Fabio]

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

What do you mean with "fixed"? I have tested the patch on my linux 32 and
64-bit systems where the java package is compiled from source and then
installed. It works correctly, I'll upload also the installation log. Then,
with the patched package installed, the java functionality in octave-3.6.4
works without problems.

I have just read the contents of the pre_install.m file and it contains an
imperfection (as is without the ../server/ detection). In fact on my system,
where the .../client/ dir is not present, the pre_install.m function completes
successfully because the jvm.cfg file is also present. So the user is not
warned about a missing libjvm.so library, __java__.oct needs it but looks for
it in the wrong location and the java functionality doesn't work out of the
box. The library is indeed present below .../server/ but the pre_install.m
script should detect it correctly. I'm attaching a patch to include also the
../server/ detection.

I have not tested octave-3.7.x yet but I have looked in the repository reading
the configure.ac file and the new --with-java-libdir option. It looks also for
the ../server/ alternative.

IMHO the symlink you suggest is something that can be avoided in the software
because we already know in advance that 64-bit installations don't come with a
../client/ dir. The proposed patch broadens the userbase of the java package,
I mean where it works flawlessly.

(file #28175, file #28176)
    _______________________________________________________

Additional Item Attachment:

File name: g-octave:java-1.2.9:20130524-215204.log.gz Size:3 KB
File name: pre_install.m.patch            Size:2 KB


    _______________________________________________________

Reply to this item at:

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

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