-
Notifications
You must be signed in to change notification settings - Fork 880
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 build on M1 Mac #6242
Comments
hi @zackman0010! |
@trask I did actually try it locally, and unfortunately it did break. Apparently the compiled Protobuf file from the 1.42.1 compiler used classes that were not present in the 1.6 runtime used by the gRPC instrumentation tests. I had to update the gRPC version in the test as well to finally get a successful compile. |
I went ahead and created a PR #6244 to show what versions I had to edit to get a successful compile. I only edited the gRPC version in the testing environment, the library and instrumentation environments remain on 1.6. |
@anuraaga @trask To move the conversation back to the issue after closing the PR, I did find what might be an alternative to committing the generated sources: grpc/grpc-java#7690 (comment) Essentially, put an if statement in the Gradle file to hardcode the use of the |
hey @zackman0010! can you send a PR with this change? as long as it passes CI I don't see any issue with merging it |
I would, but unfortunately any PR I submit is going to get stuck in the same CLA limbo as my existing PR. |
Got a similar error:
|
The ./gradlew assemble command fails when running on an M1 Mac.
I did some digging, and it appears that
protoc
does not support theosx-aarch_64
architecture until version3.17.3
. We don't use gRPC or Protobuf in our development, so I didn't know if just updating the compiler version here would be a breaking change.EDIT: Same issue also exists with the other artifact in the same file,
protoc-gen-grpc-java
. Current version is1.6.0
, does not support M1 Mac until1.42.1
. I'm much more certain this one is a breaking change, so I'm not sure how to proceed from there.The text was updated successfully, but these errors were encountered: