FW: mex files built with fortran having problmes linking in 3.2.2

[John W. Eaton]

On  2-Sep-2009, Mike Coyne wrote:

| From: Mike Coyne 
| Sent: Tuesday, September 01, 2009 11:31 AM
| To: address@hidden
| Subject: mex files built with fortran having problmes linking in 3.2.2
| 
| I am having problems createing a  "mex" file that can access the mx
| functions .
| 
| A simple example is in the dist examples
|  mkoctfile --mex myfevalf.f
| 
| octave --quiet --eval myfevalf
| warning: mark_as_command is obsolete and will be removed from a future
| version of Octave
| error:
| /afs/pbcell/home/mcoyne/.gnome-desktop/octave-3.2.2/octave-3.2.2/example
| s/myfevalf.mex: undefined symbol: mxgetstring_
| terminate called after throwing an instance of
| 'octave_execution_exception'
| panic: Aborted -- stopping myself...
| attempting to save variables to `octave-core'...
| save to `octave-core' complete
| Aborted
| 
| the mxgetstring_ is the fortran call to the c++  mxGetString ? 
| How do i build ? is there a library to link against? Or alteritibly what
| would be the correct wrapper function to generate the mxgetstring_
| function calling the C++ mxGetString function?
| 
| My platform is Rhel5 w/ gnu gcc/gfortran  4.4.1 

Octave doesn't provide Fortran bindings for the MEX interface.  I
consider this a missing feature, not a bug.  I would of course welcome
a patch to add them.  But before submitting a patch, it would probably
be best to discuss the implementation on the maintainers list.

The example files are in the distribution because there was some (very
incomplete) support for Fortran MEX files at one time, but it was
removed when the C MEX interface was finished.  I guess we forgot to
remove the Fortran example files and/or make a note in the docs.

jwe