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

[Mike Miller]

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

pkg-config is extensible, with the --variable option for example, so we could
start dumping a whole bunch of build-time configuration variables into the
pkg-config files as well. We could make things like 'pkg-config octave
--variable=VERSION' or 'pkg-config octave --variable=BLAS_LIBS' work.

If we go in this direction, we could leave all of the default values encoded
in pkg-config, not do any substitutions at all into mkoctfile, and have it
rely on pkg-config for all of the default variables when building.

Or we could pick some balance or some overlap between mkoctfile and
pkg-config.

As to this particular issue, I agree with Carnë, the variable naming scheme
in mkoctfile is the core problem in this bug report. The standard name LDFLAGS
should be used for options that modify the behavior of the link stage, like
-L, -R, -rpath, or -Wl,foo, etc.

For now should we add a LDFLAGS variable to mkoctfile and retain LFLAGS as an
alias for backwards compatibility?

    _______________________________________________________

Reply to this item at:

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

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