[Octave-bug-tracker] [bug #55447] mkoctfile: wrong LFLAGS warning, resets LDFLAGS

[Mike Miller]

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

I am going to try to make mkoctfile use LDFLAGS and apply it in the link stage
without printing a warning.

IMHO, backwards compatibility means that if a user sets LFLAGS, we will still
use it, but it doesn't mean that we have to also ignore LDFLAGS because we
used to ignore it.

If a new user using Octave 5 for the first time uses LDFLAGS, it should do
what they would expect without any warning or without any need to also set
LFLAGS, that just seems like the obvious right thing to do.

So again IMHO,

* user sets LDFLAGS only, mkoctfile uses LDFLAGS, no warning is printed
* user sets LFLAGS only, mkoctfile uses LFLAGS, prints a warning about the
variable being deprecated
* user sets both LDFLAGS and LFLAGS, mkoctfile prints a warning, uses LDFLAGS,
and either ignore or concatenate LFLAGS onto LDFLAGS

This is what I will try to get working.

    _______________________________________________________

Reply to this item at:

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

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