You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I'm just opening this issue here so I don't forget about it. You can probably stop reading.)
For some reason, the _nifty.so file produced by the conda recipe has an extra LC_RPATH that doesn't get properly cleaned up in the conda post-processing step. You can see it by inspecting the output of otool -l:
The second LC_RPATH entry is correct, but the first one (/miniconda2/envs/_build/lib) shouldn't be there. It references the _build environment on my machine. For most people, this will not cause any problems whatsoever. But if that directory happens to exist on your machine, then you'll get an error when you try to use nifty:
Fatal Python error: PyThreadState_Get: no current thread
That's because it's loading the wrong libpython2.7.dylib at runtime.
PS -- Note for mac users (okay, just me): diagnosing this issue was made easier with the DYLD_PRINT_RPATHS environment variable.
The text was updated successfully, but these errors were encountered:
I swichted to a new version of pybind11 which defines a cmake-function to add python modules.
This could change a lot (also this might undo some fixes...)
(I'm just opening this issue here so I don't forget about it. You can probably stop reading.)
For some reason, the
_nifty.so
file produced by the conda recipe has an extraLC_RPATH
that doesn't get properly cleaned up in the conda post-processing step. You can see it by inspecting the output ofotool -l
:The second
LC_RPATH
entry is correct, but the first one (/miniconda2/envs/_build/lib
) shouldn't be there. It references the_build
environment on my machine. For most people, this will not cause any problems whatsoever. But if that directory happens to exist on your machine, then you'll get an error when you try to usenifty
:That's because it's loading the wrong
libpython2.7.dylib
at runtime.PS -- Note for mac users (okay, just me): diagnosing this issue was made easier with the
DYLD_PRINT_RPATHS
environment variable.The text was updated successfully, but these errors were encountered: