octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Ben Abbott
Subject: [Octave-bug-tracker] [bug #55033] mkoctfile link failure on macos
Date: Mon, 31 Dec 2018 07:31:13 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.2 Safari/605.1.15

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

Based upon what I saw below (comment #13), I tried adding the expected content
of OCTAVE_LIBS and their path. The result was successful.


mkoctfile ('-v', 'example.cc',
'-L/usr/local/bpabbott/octave/lib/octave/6.0.0/', '-loctave', '-loctinterp')
g++ -std=gnu++11 -c  -I/usr/local/opt/readline/include
-I/usr/local/opt/sqlite/include -I/usr/local/opt/openssl/include
-I/usr/local/opt/gettext/include -I/usr/local/opt/icu4c/include
-I/usr/local/opt/qt5/include -I/usr/local/opt/sundials27/include
-I/usr/local/opt/zlib/include -fPIC
-I/usr/local/bpabbott/octave/include/octave-6.0.0/octave/..
-I/usr/local/bpabbott/octave/include/octave-6.0.0/octave
-I/usr/local/bpabbott/octave/include  -D_THREAD_SAFE -pthread -g -O2   
example.cc -o /var/tmp//oct-G4QR4S.o
g++ -std=gnu++11 -I/usr/local/bpabbott/octave/include/octave-6.0.0/octave/..
-I/usr/local/bpabbott/octave/include/octave-6.0.0/octave
-I/usr/local/bpabbott/octave/include  -D_THREAD_SAFE -pthread -g -O2 -bundle
-bundle_loader /usr/local/bpabbott/octave/bin/octave-6.0.0  -o example.oct 
/var/tmp//oct-G4QR4S.o   -L/usr/local/bpabbott/octave/lib/octave/6.0.0/
-loctave -loctinterp  -L/usr/local/bpabbott/octave/lib  
-L/usr/local/opt/readline/lib -L/usr/local/opt/sqlite/lib
-L/usr/local/opt/openssl/lib -L/usr/local/opt/bison/lib
-L/usr/local/opt/gettext/lib -L/usr/local/opt/libffi/lib
-L/usr/local/opt/icu4c/lib -F/usr/local/opt/qt5/lib
-L/usr/local/opt/sundials27/lib -L/usr/local/opt/zlib/lib
-L/usr/local/opt/qrupdate/lib 


I also modified mkoctfile (lines 304-305)


  vars["OCT_LINK_DEPS"] = get_variable ("OCT_LINK_DEPS", "");
//                                   "libinterp/liboctinterp.la
liboctave/liboctave.la ");


OCTAVE_LIBS contains the intended symbols.


mkoctfile -p OCTAVE_LIBS
-loctinterp -loctave 


As does OCTLIBDIR


mkoctfile -p OCTLIBDIR
/usr/local/bpabbott/octave/lib/octave/6.0.0


Should OCTAVE_LIBS and OCTLIBDIR being finding their way into the link phase
automatically?

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]