|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #55363] Global variable in a MEX file |
Date: | Mon, 7 Jan 2019 15:25:46 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 |
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/
[Prev in Thread] | Current Thread | [Next in Thread] |