The issue may be due to having skew between an old protoc version with a more up to date runtime, which is a mismatch that we don't support (this is particularly strongly true in C++ where you really need an exact version match, per https://protobuf.dev/support/cross-version-runtime-guarantee/#cpp ). Is it possible that one case is using very stale protoc compared to your standalone build that is using the intended protoc 26.1?
On Monday, January 13, 2025 at 4:31:02 PM UTC-5 James J wrote: > When compiling the bazel protobuf target as part of the Envoy project > (release 1.32.3), an error is returned saying that > PROTOBUF_ATTRIBUTE_REINITIALIZES is an 'unknown type name' in the generated > 'type.pb.h' file. > > When compiling protobuf on its own, separately from Envoy, the build > completes successfully. When comparing the files, > PROTOBUF_ATTRIBUTE_REINITIALIZES appears in the file generated during the > Envoy build, while ABSL_ATTRIBUTE_REINITIALIZES appears in the file from > stand alone build of protobuf. > > I compiled both Envoy and protobuf on the ppc64le architecture. The > release of Envoy being compiled depends on protobuf version 26.1. Is there > a build flag or configuration that determines whether > PROTOBUF_ATTRIBUTE_REINITIALIZES or ABSL_ATTRIBUTE_REINITIALIZES is > utilized in the generated files? > > Any help is appreciated. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/protobuf/84e84ec2-a502-4bae-95aa-958ed0b37089n%40googlegroups.com.
