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

[Rik]

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

mkoctfile always checks the environment variable first and uses that in
preference to anything set during the build configuration.  See
src/mkoctfile.in.cc.  For this particular example,


  vars["LDFLAGS"] = get_variable ("LDFLAGS", %OCTAVE_CONF_LDFLAGS%);


On Linux, this just generally works and the override mechanism is only used
when the user themselves have specified something.

I suspect on cross-builds anything from the build machine is likely to be
incorrect.  Does Octave's initialization file for windows (.bat or .vbs) set
up the environment variables so that mkoctfile works correctly?

If so, it may be that mkoctfile the executable should not be called directly
from the command line but needs a wrapper to set the environment variables
correctly.

I'm just guessing that the Makefile for sparsersb calls 'mkoctfile -p LDFLAGS'
directly from the command line.  An replacement, just to see if this works,
would be 


octave --eval 'mkoctfile -p LDFLAGS'




    _______________________________________________________

Reply to this item at:

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

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