|
| From: | John W. Eaton |
| Subject: | [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows |
| Date: | Tue, 29 Sep 2020 11:03:59 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 |
Follow-up Comment #21, bug #59173 (project octave):
OK, the --export-all-symbols option is added here:
http://hg.savannah.gnu.org/hgweb/octave/file/6ec04c206ac4/configure.ac#l2463
It was added in this changeset:
http://hg.savannah.gnu.org/hgweb/octave/rev/db4453f40550
See also this mailing list discussion:
https://lists.gnu.org/archive/html/octave-maintainers/2013-07/msg00171.html
I don't think this flag is specific to Java. It is added to the Octave build
flags so that the symbols from our DLLs will all be exported, the same as they
are by default on Unixy systems. The other alternative is to create export
lists and export only those symbols that we choose to make visible.
It's not clear to me whether this flag would be needed by packages, though we
do need something that will export at least the symbols necessary for loading
.oct file functions.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59173>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |