Pangolin built on python 3.7.4 results in seg fault 11

[dragonSwords98]

Hello,

I ran the cmake step for pangolin using the usual steps in a conda base env of python 3.7.4 (my MACOSX is using 3.7.7 from brew), and it detects the libraries just fine. Everything will build. But eventually when I go to python3 to import pangolin, it will result in a seg fault 11. Does anyone know what I can do?

(base) MacBook-Pro:build bryanling$ cmake -DBUILD_PANGOLIN_FFMPEG=OFF ../
-- The C compiler identification is AppleClang 10.0.1.10010046
-- The CXX compiler identification is AppleClang 10.0.1.10010046
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Build type not set (defaults to release)
-DCMAKE_BUILD_TYPE=Debug for debug
-- Python Found and Enabled
-- Eigen Found and Enabled
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2") 
-- libpng Found and Enabled
-- libjpeg Found and Enabled
-- libtiff Found and Enabled
-- libzstd Found and Enabled
-- Found Doxygen: /usr/local/bin/doxygen (found version "1.8.17") found components: doxygen dot 
CMake Warning at python/CMakeLists.txt:3 (find_package):
  By not providing "Findpybind11.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "pybind11",
  but CMake did not find one.

  Could not find a package configuration file provided by "pybind11" with any
  of the following names:

    pybind11Config.cmake
    pybind11-config.cmake

  Add the installation prefix of "pybind11" to CMAKE_PREFIX_PATH or set
  "pybind11_DIR" to a directory containing one of the above files.  If
  "pybind11" provides a separate development package or SDK, be sure it has
  been installed.


-- Found PythonInterp: /Users/dragonSwords98/miniconda3/bin/python3.7 (found version "3.7.4") 
-- Found PythonLibs: /usr/local/Frameworks/Python.framework/Versions/3.7/lib/libpython3.7m.dylib
-- Performing Test HAS_CPP14_FLAG
-- Performing Test HAS_CPP14_FLAG - Success
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- LTO enabled
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/dragonSwords98/PycharmProjects/pangolin-uoip/build

after make -j8

[100%] Built target pangolin
(base) MacBook-Pro:build dragonSwords98$ import python
(base) MacBook-Pro:build dragonSwords98$ cd ..
(base) MacBook-Pro:pangolin-uoip dragonSwords98$ python setup.py install
running install
copying ./pangolin.cpython-37m-darwin.so -> /
(base) MacBook-Pro:pangolin-uoip dragonSwords98$ python3
Python 3.7.4 (default, Aug 13 2019, 15:17:50) 
[Clang 4.0.1 (tags/RELEASE_401/final)] :: Anaconda, Inc. on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pangolin
Segmentation fault: 11

I know this worked on 3.6.5 at some point. My next strategy would be to hack the cmakes so they detect conda's 3.6 instead of the higher version of 3.7.7 from brew. However, this has so far been a headache as well.

Any suggestions?

[kenmaro3]

@dragonSwords98
hello, I was struggling to build pangolin with python 3.7 with macOS catrina and found your post.

I have the same issue import pangolin --> seg fault 11

if you found way around for this, could you please share the hint in here?

thanks in advance.

[lupusorina]

I have the same issue. seg fault after importing it with python 3.9

[dragonSwords98]

@lupusorina Apologies, it has been a really long time since I was playing with this.

iirc, I ended up setting it up differently. I think you could look into what @kenmaro3 did. It sounds like what they did in his mention is along the lines of what my successful attempt.

Hopefully it helps to hear from someone at least.