Thu 23 May 2013 07:39:34 PM UTC, comment #8:
The "timestamp.... " stuff looks an operating system issue to me.
As to JDK: I'm no Java low-level expert, but AFAIK a JDK comprises a JRE.
The Java package installation hard-codes the libjvm.so location from the JDK, not from the JRE.
But an other, more important issue is that you have a 64-bit system, where the jvm is often not in .../client but in .../server.
Usually it suffices to make a symlink in .../server to .../client/libjvm.so
Unfortunately the Java package isn't prepared to catch this for 64-bit systems, and it may never be as Java will be in core Octave in the next stable release - soon to come out.
BTW please move this thread to the help-octave mailing list, do not hijack an old and fixed-bug tracker thread. I think I'll close/lock the discussion.
|
Wed 22 May 2013 10:04:44 PM UTC, comment #7:
Ok, I have found the problem. I have opened also the new bug #39045 because is potentially related to all the octave forge packages.
Now I have the java package installed but I have still a minor issue. When I execute a function of the java package I got the following error:
octave:5> javamem
warning: timestamp on file /etc/java-config-2/current-system-vm/jre/lib/amd64/client/libjvm.so is in the future
error: java_invoke: /etc/java-config-2/current-system-vm/jre/lib/amd64/client/libjvm.so: failed to load: /etc/java-config-2/current-system-vm/jre/lib/amd64/client/libjvm.so: cannot open shared object file: No such file or directory
error: called from:
error: /usr/share/octave/packages/java-1.2.9/javamem.m at line 65, column 6
/etc/java-config-2/current-system-vm is a symlink to the current java installation (it's managed in this way on Gentoo).
What happens is that libjvm.so is not found because I have installed a JDK and not a JRE. On my system the file is installed below /etc/java-config-2/current-system-vm/jre/lib/amd64/server/libjvm.so
What do you think? Can this be fixed at package level or should it be fixed at distribution level?
|
Mon 20 May 2013 01:25:04 PM UTC, comment #6:
java_invoke is a compiled function living in _java_.oct (in the /usr/local/lib/octave/packages/../java-1.2.9 subdir).
Did you set JAVA_HOME properly?
Do you have a 32 or 64 bit system?
What does "uname -a" say (at the bash prompt?
Is there (in Octave) a directory /usr/local/lib/octave/packages/.../java-1.2.9 in the path? ( ... stands for your arch, just type "path" and check Octave's output)
|
Sun 19 May 2013 11:45:24 PM UTC, comment #5:
I'm sorry, I was trying to install an older version of java package, not it installs but it still doesn't work correctly :-( I'm working under linux
octave:1> pkg list
Package Name | Version | Installation directory
---------------+---------+-----------------------
java *| 1.2.9 | /usr/share/octave/packages/java-1.2.9
octave:2> system ("javac -version")
javac 1.6.0_45
ans = 0
octave:2> javamem
error: 'java_invoke' undefined near line 65 column 8
error: called from:
error: /usr/share/octave/packages/java-1.2.9/javamem.m at line 65, column 6
I don't see the java_invoke.m function definition in the package. Should I open a new bug report?
|
Sun 19 May 2013 10:44:23 PM UTC, comment #4:
A few more details would be helpful.
|
Sun 19 May 2013 10:00:50 PM UTC, comment #3:
The same still applies to octave 3.6.4
|
Mon 14 Feb 2011 10:43:44 PM UTC, comment #2:
John, that msg you referred to was about an issue with another variable.
I've already answered the original poster through the OctDev (octave-forge) mailing list, see here:
http://sourceforge.net/mailarchive/message.php?msg_id=27059390
Thx
|
Mon 14 Feb 2011 07:51:56 PM UTC, comment #1:
To avoid this problem, you just need to rename the variable in the java package to something else.
https://mailman.cae.wisc.edu/pipermail/help-octave/2011-February/044625.html
|
Mon 14 Feb 2011 03:09:43 PM UTC, original submission:
I tried to install a java package, java-1.2.7.tar.gz, on Octave 3.4.0 installation but it failed with the following error:
|