[Octave-bug-tracker] [bug #53627] build: oct files should not need to link with -loctinterp -loctave

[Andrew Janke]

Follow-up Comment #12, bug #53627 (project octave):

While we're on this subject: it would be nice if oct files also did not link
to liboctinterp and liboctave on macOS. The presence of those dylib links
means (I think) that a given octfile is only compatible with an Octave that is
installed in the same location as the original Octave that produced those
octfiles.

For example, this is what I see for the octfiles produced by the control
package:



$ pwd
/Users/janke/octave/control-3.1.0/x86_64-apple-darwin17.6.0-api-v52
$ otool -L __control_helper_functions__.oct
__control_helper_functions__.oct:
        /usr/local/opt/octave/lib/octave/4.4.0/liboctinterp.5.dylib 
(compatibility
version 6.0.0, current version 6.0.0)
        /usr/local/opt/octave/lib/octave/4.4.0/liboctave.5.dylib (compatibility
version 6.0.0, current version 6.0.0)
        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version
400.9.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
1252.50.4)


This has shown up as an issue for a user who's interested in using both a
Mac-style Octave.app and a Homebrew-installed octave on the same system:
http://lists.gnu.org/archive/html/octave-maintainers/2018-07/msg00101.html.
It's of interest to me also, because I would like to be able to install
multiple versions and variants of Octave side-by-side on the same machine for
testing.

Is there anything I can do to help figure out how to do this on macOS?

    _______________________________________________________

Reply to this item at:

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

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