Matlab engine for python segfaults in matlab.engine.start_matlab() (Matlab R2014b, OS X)
Ältere Kommentare anzeigen
I recently started experimenting with interfacing Python and Matlab. I need to use Anaconda Python distro. As mentioned in other answers, e.g. here , I use
export DYLD_LIBRARY_PATH=/anaconda/lib:${DYLD_LIBRARY_PATH}
which allows me to import matlab.engine without segfaulting, but any time I try to run matlab.engine.matlab_start(), I get the usual "Segmentation fault 11" in libpython2.7.dylib. This is driving me a little crazy; is there a known solution for this?
2 Kommentare
Nick Barry
am 25 Jun. 2015
Same problem. Any luck solving this?
Craig
am 8 Aug. 2015
Exactly the same problem, running anaconda as well. I think it's something to do with dynamic linking - see https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/fUpqjkK5jEI
Did you solve this in the end or give up? Cheers, Craig
Antworten (2)
Any Luck with this? I think it's something to do with dynamic linking in anaconda that I don't understand.
Linking directly to the system lib seems to work for me, using Anaconda.
export DYLD_LIBRARY_PATH=/System/Library/Frameworks/Python.framework/Versions/2.7/lib:$DYLD_LIBRARY_PATH
1 Kommentar
Shourya Sonkar Roy Burman
am 10 Nov. 2015
Bearbeitet: Shourya Sonkar Roy Burman
am 10 Nov. 2015
Thanks that really helped.
Ryan
am 9 Sep. 2015
0 Stimmen
Same issue; seems like not too much to ask that these features install properly
Kategorien
Mehr zu Call MATLAB from Python finden Sie in Hilfe-Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!