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
Unable to install grpcio 1.51.0 for Python on Mac OS Apple M1 #31737
Comments
Can you please upload the full logs? The line that has all of the information is somewhere in the clang invocations. |
This seemed to fix it for me:
|
Just to confirm that this is happening on arm based macs. |
I think @atrbgithub 's suggestion was correct. The issue here is definitely a lack of openssl installed. To the folks experiencing this issue, is this actually a case where things were working fine on 1.50 and they are now not working well on 1.51? I was under the impression that boringssl did not function on M1. |
@gnossen yes, I've just solved the problem for my dependency forest by pinning |
1.51.0 has been yanked. For those affected, please consider testing against our release candidates in the future by adding a test job that installs with |
Well, I think we need to figure out some of the differences. Environment first:
I couldn't install grpcio1.50.0(use boringssl by default) successfully. Here's
This's similar to people discussed in #25082, but there's a slight difference in outputs: macosx-10.9-universal2 on my m2 mac and macosx-11-arm64(on m1?). And successfully installed grpcio1.51.0rc1(use system openssl by default):
So, what causes such different results between us? I continued trying to unset
🤔
Which situation is more suitable for developers? Or grpc should improve build scripts to adapt these situations. |
For what it's worth, my automated build of grpcio 1.51.0 on macOS M1 went fine. I used |
@amchii |
@gnossen It's full log, you just click view the full file, will see output
Note, boringssl works exactly on my m2 mac, but will failed if I set (my default) env vars:
|
It looks like this is the actual issue:
Looks like it's just a symbol clash been boringssl and openssl. |
Since cibuildwheel can cross compile grpc on intel mac (but seems can not tests |
@pietrodn Thanks! |
I believe so. I'm working on that at the moment. |
@gnossen any progress on this you could share with us? Maybe an ETA would be great :) |
The code changes for this are complete and universal2 artifacts will be published with the next release. |
Awesome thank you 👏 |
poetry install Resolved my issue |
What version of gRPC and what language are you using?
grpcio==1.51.0
grpcio-tools=1.51.0
What operating system (Linux, Windows,...) and version?
Mac OS Ventura (Apple M1) 13.0.1
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.11.0 / 3.10.8 / 3.9.15
What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.
I wanted to upgrade a Poetry project depending on
grpcio
, and I'm facing asetuptools
errors while trying to install the new wheel.I've tried to install the project manually through
pip
with this command line:And I was still unable to update my project dependency.
What did you expect to see?
A successful installation.
What did you see instead?
I've got the same output for Python 3.10 and 3.11.
Anything else we should know about your project / environment?
My project is setup thanks to Poetry with the following
pyproject.toml
subset:The text was updated successfully, but these errors were encountered: