[Octave-bug-tracker] [bug #55363] Global variable in a MEX file

[Guillaume]

Follow-up Comment #3, bug #55363 (project octave):

Thanks for the feedback. I don't think it's a regression though: one of the
tests is with Octave 4.4.0 because that's the latest version available as a
package on that platform. The fact that it works for you is interesting as it
could then be due to a difference in compiler, between gcc 7.3 and 8.2, even
if I cannot understand how yet.

Reading more about exporting symbols in shared libraries, I wonder if
mkoctfile should use an export map:

https://accu.org/index.php/journals/1372


{
  global:
    mexFunction;
  local:
    *;
};


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55363>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/