-
Notifications
You must be signed in to change notification settings - Fork 220
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
Apple Silicon (M1, M2,...) Not Supported #338
Comments
Currently working with the pytorch team to determine if this crate is the cause of this issue - pytorch/pytorch#96959 (comment) |
This looks like an issue linked to the upstream dependency tch rather than this crate |
Duplicate of #326 |
You can close this issue if you want and pass the buck on to another library - there is currently no documentation on how to build this library from scratch using an Apple Silicon chip, even after reinstalling homebrew, anaconda and python. The three files mentioned are incorrectly linked and there hasn't been any documentation on how to fix this that works. |
@patientplatypus6 Were you able to find a solution to this issue?? Getting the exact same thing. Thanks! |
I'm opening a new issue here because I believe that Apple M1 may not be supported. I've posted a comment on here (#326), but this needs to be at the top of the cue, given that Apple Silicon is the latest architecture and this is the only AI tool for sentiment analysis on crates.io. (i.e. if this library works I think it's important).
The issue is claimed to be solved in the other thread. It is not.
According to the most recent documentation versions of pytorch 1.13+ work for Apple Silicon. Here is my latest architecture according to the pytorch documentation - (and a bug report submitted here pytorch/pytorch#96959) -
I've opened a github issue here - https://stackoverflow.com/questions/75752140/installation-of-transformer-library-not-working-in-apple-m1.
I'm excited to use this library, once an implementation for Apple Silicon is demonstrated to work.
The text was updated successfully, but these errors were encountered: