[Octave-bug-tracker] [bug #48678] mkoctfile returns linker flags on LFLAGS instead of LDFLAGS

[John W. Eaton]

Follow-up Comment #4, bug #48678 (project octave):

The LDFLAGS variable is normally empty and allows the user to add options by
setting LDFLAGS in the environment.

It looks like the LFLAGS variable is just there to ensure that -L$(octlibdir)
is included in the linker options when it is not a directory that is normally
searched by the linker.  I suppose it is similar to AM_LDFLAGS in automake. 
LFLAGS may not be the best name, but this job needs to be done in some way. 
It's probably best to keep it separate from LDFLAGS so that if someone sets
LDFLAGS in the environment, they don't have to also include
-L/usr/local/octave/lib/.../whatever.  Users should be able to set LDFLAGS
independently and still expect things to work.

    _______________________________________________________

Reply to this item at:

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

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