[Octave-bug-tracker] [bug #39454] Fix building core Java support for MinGW builds

[Rik]

Follow-up Comment #5, bug #39454 (project octave):

I haven't been following this issue closely since I only build on a Linux
platform.  My suggestion that the attached changeset seemed reasonable was
based on the fact that

1) It is narrowly scoped.  The clause is protected by a case statement so only
affected users on MinGW and Cygwin would see a change.  Everyone else should
be undisturbed by it.

2) It is narrowly targeted.  It only attempts to fix compiling Octave on MingW
WHEN ALSO compiling Java.

There is no real reason to suppose linearity, but I prefer the small change in
the hopes that if something goes wrong it also goes wrong in a small way. 
Since I won't feel the pain, I'm willing to leave it up to you two to decide
whether you want to switch all of MinGW compiling to use --export-all-symbols.
 If we do do that, is there any reason to still create .def files such as
ranlib.def and cruft.def?  Or could we remove those from the build system?



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39454>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/