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

[Markus Mützel]

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

It looks like LDFLAGS is passed too early in the flags that mkoctfile uses.
That is what I would like to change on stable with
"bug59173_3-mkoctfile_LDFLAGS_last_stable.patch".
When that is done, packages can start the transition from using LFLAGS to
LDFLAGS and still be able to compile for Windows.

Packages currently *have* to use LFLAGS if they want to be able to compile for
Windows. That means maintainers couldn't start making the change as advised in
the current deprecation message.

If we fix that now, I think we should give the two versions transition time
that we usually have for deprecation - starting from now. So if we start to
support using LDFLAGS now on stable, we could remove LFLAGS in Octave 8 (not
Octave 9 like I wrote before).

I think that the other two patches are an improvement compared to the current
behavior. But I am not 100% convinced that they can be applied without any
side effects. That is why I would like to apply them on default (given that
Octave 6 is hopefully close to release).
If we are sure that they won't cause any harm, we could also apply the on
stable. But that wouldn't change the previous points.

Both patches might cause different issues. That is why I would prefer to apply
them separately.

    _______________________________________________________

Reply to this item at:

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

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