Recently our macOS builds have started to fail with the following error:
Running appleseed.python unit tests... Traceback (most recent call last): File "sandbox/lib/Debug/python/appleseed/test/runtests.py", line 31, in <module> from testbasis import * File "/Users/travis/build/appleseedhq/appleseed/sandbox/lib/Debug/python/appleseed/test/testbasis.py", line 30, in <module> import appleseed as asr File "/Users/travis/build/appleseedhq/appleseed/sandbox/lib/Debug/python/appleseed/__init__.py", line 41, in <module> from _appleseedpython import * ImportError: dlopen(/Users/travis/build/appleseedhq/appleseed/sandbox/lib/Debug/python/appleseed/_appleseedpython.so, 2): Library not loaded: libSeExpr.dylib Referenced from: /Users/travis/build/appleseedhq/appleseed/sandbox/lib/Debug/python/appleseed/_appleseedpython.so Reason: unsafe use of relative rpath libSeExpr.dylib in /Users/travis/build/appleseedhq/appleseed/sandbox/lib/Debug/python/appleseed/_appleseedpython.so with restricted binary
This used to work fine until less than a month ago.
Here is a full build log:
Here is our build script:
I have found this topic on Stack Overflow:
It seems that we could fix (or rather, work around) the problem by using
install_name_tool to change
_appleseedpython.so, but why would we suddenly need to do that? What changed?