Skip to content
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

gcc failed: error executing CppCompile command with Bazel@HEAD #1938

Open
sgowroji opened this issue Oct 17, 2023 · 3 comments
Open

gcc failed: error executing CppCompile command with Bazel@HEAD #1938

sgowroji opened this issue Oct 17, 2023 · 3 comments

Comments

@sgowroji
Copy link

https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3391#018b3bcb-2713-4f8b-a4bf-bc799cf8a92d
Platform : Ubuntu
Logs:

ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/595e58dc908d146f3afb937d2a9250aa/external/com_github_googlecartographer_async_grpc/async_grpc/BUILD.bazel:49:11: Compiling async_grpc/event_queue_thread.cc failed: (Exit 1): gcc failed: error executing CppCompile command (from target @com_github_googlecartographer_async_grpc//async_grpc:async_grpc)

Steps:

git clone -v https://github.com/googlecartographer/cartographer.git
git reset ef00de2317dcf7895b09f18cc4d87f8b533a019b --hard
export USE_BAZEL_VERSION=2ddacab80af1dca3c04e74809827c47ec4bc8498
bazel build ...

CC Greenteam @fweikert

@sgowroji
Copy link
Author

Hi @wohe, Can you have a look at the above issue. Thanks!

@Wyverald
Copy link
Contributor

Wyverald commented Nov 9, 2023

Hmm, for some reason our culprit finder pinned this on --enable_bzlmod being flipped to true (https://buildkite.com/bazel/culprit-finder/builds/7854#018bb242-8678-4450-ba11-32be8e342f96). The error message suggests nothing that would incriminate Bzlmod, though... will have to dig a bit more.

@Wyverald
Copy link
Contributor

Wyverald commented Nov 9, 2023

Hmm, this is probably because the bundled protobuf in @bazel_tools when Bzlmod is enabled is a higher version than what Cartographer's WORKSPACE says, and that one has an incompatible API change.

Given that this repo hasn't seen a commit in over a year, I'll just go ahead and disable Cartographer from Bazel CI.

Wyverald added a commit to bazelbuild/continuous-integration that referenced this issue Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants