I am trying to build this repo
https://github.com/andrewkatson/protobuf_not_included using gcc 13.2.0 on Windows 10 with bazel 7. And I get many errors like this one:
Starting local Bazel server and connecting to it...
INFO: Analyzed 3 targets (132 packages loaded, 4243 targets configured).
ERROR: C:/bazel-bin/external/protobuf~23.1/src/google/protobuf/BUILD.bazel:184:11: Compiling src/goo
gle/protobuf/port.cc [for tool] failed: absolute path inclusion(s) found in rule '@@protobuf~23.1//s
rc/google/protobuf:port_def':
the source file 'src/google/protobuf/port.cc' includes the following non-builtin files with absolute
paths (if these are builtin files, make sure these paths are in your toolchain):
'C:/bazel-bin/external/protobuf~23.1/src/google/protobuf/port_def.inc'
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 8.789s, Critical Path: 1.09s
INFO: 69 processes: 37 internal, 32 local.
ERROR: Build did NOT complete successfully
My command line looks like this bazel --output_base="C:\bazel-bin" build --extra_toolchains=@local_config_cc//:cc-toolchain-x64_windows_mingw --extra_execution_platforms=//:windows-mingw-gcc :all --compiler=mingw-gcc --host_compiler=mingmw-gcc
My current guess is that something between protobuf and gcc on Windows is causing friction. I have already asked the bazel boost people what they think here:
https://github.com/bazelboost/registry/issues/173 but we determined this is likely a protobuf thing not an interaction.
Has anyone seen this before?