Open q0dr opened 1 month ago
Reproduced issue above with Bazel 7.1.2, note that this seems to be Mac specific (maybe arm64 specific) as all our py targets work fine on linux builds.
Running into the same issue with Bazel 6.5.0 on a M1 Mac with Sonoma 14.6
@q0dr We don't claim support of MODULE.bazel . We'll welcome any contribution to add support for this.
I was able to reproduce this in a gist, Reproduction of grpc/grpc#37251, and to fix it in https://github.com/bazelbuild/bazel-central-registry/pull/2685. Though by the looks of the presubmit checks, this may necessitate releasing an updated module version instead.
https://github.com/bazelbuild/bazel-central-registry/pull/2685 is in. @q0dr can you update your grpc module to version 1.66.0.bcr.1 and see if it fixes your build?
What version of gRPC and what language are you using?
gRPC 1.63.1 python 3.12.1
What operating system (Linux, Windows,...) and version?
macOS Sonoma 14.5
What runtime / compiler are you using (e.g. python version or version of gcc)
python 3.12.1
What did you do?
I have a test that demonstrates that with Bazel 7.2.0, protobuf 27.1 and gRPC 1.63.1, a gRPC service written in Python fails to build on a MacBook Pro with an Apple M3 Pro chip.
My MODULE.bazel file:
My BUILD.bazel file:
My service.proto file:
When I do:
I get:
followed by several thousand more lines complaining about undefined symbols, all of which start with _Py or __Py. This seems to come from Cython, which gRPC apparently depends upon for Python.
If I try to build a C++ service using:
The build succeeds.
What did you expect to see?
A successful build.
What did you see instead?
See above.
Anything else we should know about your project / environment?
Nothing that I can think of. I'm happy to answer questions.
NOTE: This is also filed as https://github.com/grpc/grpc.io/issues/1307