[Octave-bug-tracker] [bug #55033] mkoctfile link failure on macos

[Mike Miller]

Follow-up Comment #9, bug #55033 (project octave):

You'll want to trace those variables yourself to see what the values are and
where they come from.

mkoctfile.cc comes from mkoctfile.in.cc by way of a set of sed substitions.
The script that calls sed is build-aux/subst-cross-config-vals.sh, which is in
turn built from build-aux/subst-cross-config-vals.in.sh. I think you'll see
that it all traces back to variables defined in configure.

Like I said, there needs to be one set of linker options for building oct
files inside of the Octave build tree, before mkoctfile exists, and another
set of linker options for building oct files outside of the Octave build,
after Octave is installed and mkoctfile exists.

On my system these are all empty strings so I can't easily compare notes
against a system where they need to be defined correctly.

    _______________________________________________________

Reply to this item at:

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

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