-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined symbols for architecture x86_64 on OSX Big Sur #101
Comments
I wanted to ping again because I am still limping along using my linux machine as a workaround. Ideally I would like to use this on the mac since most of my fellow devs at work all use macs. I'm not sure if this is a problem within a language-binding issue or tree-sitter core specifically. @maxbrunsfeld do you happen to know where this problem is coming from? Based on some research it sounds like switching from |
I think we should close this and you should subscribe to this issue instead: tree-sitter/py-tree-sitter#41. I would say that this is an issue with The symptom you're seeing is a bit different (in that on macOS, |
In case anyone else runs across this issue, here is the resolution: The issue boiled down to the recent OSX breaking how the ctypes.util.find_library command works in python, always returning None (example error, issue 1 in cpython, issue 2 in cypthon). The find_library command is used within py-tree-sitter in order to see if the c++ or stdc++ libraries are available and loading one of them (see discussion). Since None is always returned, the necessary libraries are never loaded. However, the actual load_library works. I did not have access to the patched versions of python so monkey patching around the load_library to just return anything is enough to get this system back up and running. Here is my monkey patch, which is a variation of the patch listed here:
|
Wow, thanks for sharing your findings! |
My pleasure! This looks like an issue that will eventually resolve itself (at least in python 3.8/3.9), so this is hopefully just a temporary workaround in the meantime. |
Hi tree-sitter-python,
I was able to develop using
tree-sitter-python
without any issues until I upgraded my computer to OSX Big Sur. Now I'm running into the following error:To add to this mystery I've been able to build
tree-sitter-java
,tree-sitter-javascript
, andtree-sitter-scala
successfully, however also run into the error when attemptingtree-sitter-cpp
.I've played around with different versions of
python 3
(to see ifclang
was the issue) to no avail. Ex onpython 3.6
:I've also tried different versions of
tree-sitter
andtree-sitter-python
and seen the error consistently in every variation:tree-sitter 0.19.0
andtree-sitter-python 0.19.0
, as well astree-sitter 0.2.0
and the versions oftree-sitter-python 0.13.6 - 0.17.1
.I also have a linux machine and don't have any problems over there.
Do you know where this issue is coming from and how to get around it?
Thank you!
The text was updated successfully, but these errors were encountered: