-
Notifications
You must be signed in to change notification settings - Fork 15.5k
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
[Build] Failure to build with "no matching function for call to 'StrongPointer()'" #16868
Comments
DEBUG: /home/mnidev/.cache/bazel/_bazel_mnidev/3c3a08606d72aa32889b958d96f38c5b/external/system_ruby/bundle.bzl:3:10: WARNING: no system ruby found for bundle Seeing this same issue. Think before commiting to main a CI test would have caught. ERRORS: |
Some versions of gcc seem to advertise __cpp_nontype_template_args but not support the argument in some cases. Only attempt the template parameter if we are using the optimized .reloc approach. Fixes protocolbuffers#16868 PiperOrigin-RevId: 634787159
Some versions of gcc seem to advertise __cpp_nontype_template_args but not support the argument in some cases. Only attempt the template parameter if we are using the optimized .reloc approach. Fixes #16868 PiperOrigin-RevId: 634787159
For the record: ref: https://repology.org/project/gcc/badges protobuf/src/google/protobuf/port.h Lines 66 to 76 in 63def39
|
After using offical boost 1.83.0[1], rules_cc@0.0.13 are required, which, in turn, requires Protobuf v27.0. Protobuf v27.0 is not compatible with GCC less than 13[2]. [1] apache#2789 [2] protocolbuffers/protobuf#16868
After using offical boost 1.83.0[1], rules_cc@0.0.13 are required, which, in turn, requires Protobuf v27.0. Protobuf v27.0 is not compatible with GCC less than 13[2]. [1] #2789 [2] protocolbuffers/protobuf#16868
What version of protobuf and what language are you using?
Protobuf commit 9f40411
What operating system (Linux, Windows, ...) and version?
Linux Debian 11 using Docker
What runtime / compiler are you using (e.g., python version or gcc version)
gcc 12
What did you do?
Build protoc using cmake
What did you expect to see
Successful build
What did you see instead?
Build failure with log
Anything else we should know about your project / environment
us-docker.pkg.dev/grpc-testing/testing-images-public/grpc_artifact_protoc_aarch64:be8fc962f6a27ce976abecbda3dd02be4be5683d@sha256:a0f6b544c1b2fa75f73b26cb28281917153304e9df2789e93de0732494e6b651
The text was updated successfully, but these errors were encountered: