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

[Mike Miller]

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

So Matlab provides a boilerplate version script file that it passes to the
linker to ensure that only the mexFunction symbol is exported in the dynamic
symbol table? Octave can do that as well if there is no other way to deal with
this. I do not think Octave should be in the business of parsing LDFLAGS and
trying to remove individual options that the user or distribution
intentionally added.

    _______________________________________________________

Reply to this item at:

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

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