RE: Debugging mex error in Octave: undefined symbol: mxcopyreal8toptr_

[Anthony Gitter]

Hi Mike,
Thanks, that is very informative and will guide my next steps.  I expect there 
are other undefined functions in this code and will need to investigate that 
further.

The Fortran mex interface is important in order to use this particular 
third-party package that was originally written for MATLAB.  I'm haven't 
written Fortran code before, so I don't think I could successfully contribute 
to adding this support to Octave.

Thanks,
Anthony

P.S. Thanks also for the Octave Docker containers you maintain.  They are 
perfect for continuous integration testing. 

-----Original Message-----
From: Mike Miller [mailto:address@hidden 
Sent: Friday, April 5, 2019 12:34 PM
To: Anthony Gitter <address@hidden>
Cc: address@hidden
Subject: Re: Debugging mex error in Octave: undefined symbol: mxcopyreal8toptr_

On Fri, Apr 05, 2019 at 14:31:53 +0000, Anthony Gitter wrote:
> I am attempting to compile a mex file from third-party Fortran code. I 
> receive the error message:
> error: glmnetControl: /SCINGE/glmnet_matlab/glmnetMex.mex: failed to 
> load: /SCINGE/glmnet_matlab/glmnetMex.mex: undefined symbol: 
> mxcopyreal8toptr_

This function, and all of the other functions in 'fintrf.h' include file, are 
not currently part of Octave's mex interface. In general, Octave does not 
implement the Matlab Fortran mex interface at all, only the C interface.

If this is the only undefined function in your project, you could try compiling 
in the example implementation in the old mailing list thread that you pointed 
to.

Is the Fortran mex interface important to your use of Octave? Would you like to 
help to add that capability to Octave?

--
mike