[Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows

[Markus Mützel]

Follow-up Comment #12, bug #59173 (project octave):

Dang! The problem I had with the sparsersb package wasn't caused by the wrong
LDFLAGS but by me not knowing the right way to do things. Sorry for that.

Still, the flags returned by mkoctfile look strange.
But maybe we can lower the priority until we find a real life problem.

The change that Rik proposes in comment #11 is much less intrusive and might
be what is expected since LDFLAGS should be used as a replacement of the
deprecated LFLAGS. And that change will make `mkoctfile -p LDFLAGS` return the
same that `mkoctfile -p LFLAGS` returned previously.
Is it ok that additional flags (like "-Wl,--export-all-symbols" from comment
#0) might be lost?

    _______________________________________________________

Reply to this item at:

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

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