[Octave-bug-tracker] [bug #48378] native doInvoke() fails from Java method called from Octave

[Mike Miller]

Update of bug #48378 (project octave):

              Item Group:              Regression => Incorrect Result       
                  Status:                    None => Confirmed              
                 Release:                   4.0.2 => dev                    

    _______________________________________________________

Follow-up Comment #2:

Thanks for the bug report. Confirmed here on Debian on the default branch and
version 3.8.2 as well.

I don't think we can call this a regression because the Java functionality was
only added to Octave in version 3.8, so if it didn't work there, it just has
never worked properly (and hasn't been noticed or reported properly until
now).

I can confirm that it does work in the old java package on Octave 3.6, so
something must have been lost when it was imported into Octave proper.

I think we need something like the following line in Octave.java


System.load (System.getProperty ("octave.java.path") + java.io.File.separator
+ "__java__.oct");


In addition the java package started the JVM with a -Doctave.java.path=DIR
argument, so the above path could be resolved.

We'll need some similar mechanism to pass the path to liboctinterp.so into
Java so the library can be loaded to resolve these native library routines.

    _______________________________________________________

Reply to this item at:

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

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