This seems to be a transitive dependency, i.e. libcouchbase.2.dylib->libSystem.B.dylib ->libsystem_coretls.dylib - just going to talk to the libcouchbase maintainer to determine if this is a known issue, so we can arrive at a permanent fix to this problem in the next release.
Is this workaround satisfactory for the time being?
Ah, possibly it requires you to disable System Integrity Protection temporarily to achieve this… However, on inspection of my Sierra machine, it appears that the renaming has already occurred, and I can compile/link with no issues. Have you just upgraded from an older OS? Perhaps there is something cached. If you have been trying to build from a git checkout, could you try: rm -rf build/ && python setup.py --buildext --inplace && python setup.py install ?
If this fails, perhaps try building libcouchbase from source by checking out from the couchbase/libcouchbase repository on GitHub, as follows:
git clone http://github.com/couchbase/libcouchbase.git cd libcouchbase && export LCB_DIR=$PWD && cmake -G 'Unix Makefiles' && sudo make install
I was able to compile libcouchbase after installing cmake using the steps provided, but unfortunately the couchbase-python-client fails the same way as previously mentioned, even after creating a new build directory with no reference to a previously attempted install/compile.
The upgrade to high sierra was from the previous latest version so it wasn’t a massive jump up to the latest or anything.
Thanks for the reply. That’s interesting… Perhaps there was some transitional code in Sierra that allows it to work. Will try to get this fixed permanently, but in the meantime, I can only suggest disabling SIP, making the symlink, enabling SIP, rebooting and trying to build again.
I suppose this should have the advantage that it will work with the stock PyPi packages, but hopefully we will come up with a proper solution in the very near future.
Disabled SIP and ran sudo ln -s /usr/lib/libsystem_coretls.dylib /usr/lib/system/libsystem_coretls.dylib which allowed me to compile the couchbase-python-client.
Hi @jmernster, we have been trying to reproduce this on our High Sierra installs for a while but not come across the same issue. Have you seen it on any other High Sierra systems?
Unfortunately I only have access to this one laptop that I experienced the issue on. It’s not a brand new laptop/fresh install so perhaps a combination of previous sdk installs, using brew and/or compiled installations created some sort of conflict/problem along the way. If you guys aren’t seeing the same issue then I wouldn’t spend too much time on it, especially since you were able to find a solution/workaround.