Hi Evey,
Can you please provide more information about the protobuf/protoc
version that is installed in the machine, as well as the compiling
log?
- The protobuf/protoc version can be obtained by running "protoc --version".
- The compiling log can be obtained by using the --verbose option of
Hi folks. I haven't dug into this too deeply, but it sounds like protobuf
may also define NDEBUG, and it may leak into the rest of gem5? If that's
what's happening, ideally we'll be able to get protobuf to stop doing that,
etc., and we should look into how. A simpler approach to get you unstuck
[AMD Public Use]
Hi Evey,
I've seen similar issues in the past caused by protobuf. I was able to
workaround this by passing a non-existent command to the PROTOC variable to
scons, e.g.:
scons build/X86/gem5.opt -j 9 PROTOC=asdf
Due to the way gem5 stores the build variables, I never had to
