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

[Andrew Janke]

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

I've attached file #44589:  macos-bundle-undefined-dynamic_lookup-v2.patch,
which is my latest attempt to get `-undefined dynamic_lookup` working. It's
getting closer, but not there yet.

With this, the build succeeds. Though I have to do an explicit
`--disable-no-undefined` with `configure`.

The oct files it produces do not have the liboct/libinterp linkage.


$ otool -L __control_helper_functions__.oct
__control_helper_functions__.oct:
        /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)


And they work when run.


octave:4> pkg load control
octave:5> bode(ss(-1, 1, 1, 0))
octave:6>


However, the test suite crashes, and early.


octave:1> __run_test_suite__

Integrated test scripts:

  liboctave/array/Array.cc-tst ................................ PASS    
21/21
  liboctave/array/CMatrix.cc-tst ..............................fatal: caught
signal Segmentation fault: 11 -- stopping myself...
[1]    72183 segmentation fault  ./bin/octave


Mike, I'll give that "-Xlinker -undefined -Xlinker dynamic_lookup" a try if I
have some time in the next couple days. And getting that libtool.m4 logic to
activate may be the best way, but I'll need to do some work to figure out how
to do that. But it's time to call it a night for now.

    _______________________________________________________

Reply to this item at:

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

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