-
Notifications
You must be signed in to change notification settings - Fork 106
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
Compiling torch for MacOS 13 Ventura (M1) #99
Comments
Ah okay I have found your personal fork of pytorch with the nogil branch. I'll try here! |
Yeah, that’s the right branch. I haven’t built 1.13 or macOS wheels yet. I’d like to do so, but I won’t have time to look into it until next week. |
I'm actually happy with 1.9.0 but I seem to be setting segfaults building |
This is the error I'm encountering, dubiously no comment since 2021. The comment suggests cross compile should be fine, so maybe wheels will be alright... |
I'm looking into this now. I might end up building 1.13 wheels because I'm not sure 1.9.0 supports M1. |
I'm still working on building the wheels, but if you are feeling impatient you can try:
And once you install the prerequisites, build it with:
Functorch doesn't build right now because of changes to the bytecode format and PyCodeObject structure. |
I've uploaded PyTorch 1.13.1 wheels for macOS (x86-64 and arm64). Please let me know if you run into any issues. |
I'm trying to compile pytorch v.1.13.0 from source for MacOS (yes CPU only, which simplifies things) and we seem to get reaaally close before you hit something that looks pretty critical.
Is there any chance you happen to have a branch of any modifications you made to pytorch to make it compile for your custom package index? Or does this require something a little more involved?
The text was updated successfully, but these errors were encountered: