-
Notifications
You must be signed in to change notification settings - Fork 691
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
0.12.0 requires local_config_cc to be configured #1198
Comments
Thanks for creating this issue. I will look into it asap. |
rules_docker now includes an implementation for containerregistry that is go based. It's very likely the case that this go code has a dependency on a C toolchain that we cannot remove. It's also quite possible that rules_go now always requires this dependency on the C toolchain to be present (@jayconrod, can you comment if you know?). |
@nlopezgi I just commented on bazel-contrib/rules_go#2089 (comment). +1 to installing gcc or clang as a workaround. |
Thanks for your comment. Closing for now as a C/C++ toolchain is stated as a requirement for installing Bazel and it is now a hard requirement for these rules. Please let me know if for any reason anyone wants me to reopen. |
Now that
rules_docker
depends onrules_go
we have an issue where downstream users who trying to build a nodejs, or other non C++ containers, now requires C++ to be setup and configured.The specific error im getting in CI:
The defaults work on my workstation but not in CI since I don't know what system deps are required for the C/C++ tool chains to configure themselves on our CI docker container.
I think if possible we should change some config so that downstream projects don't require the C/C++ toolchains to be configured.
or
Provide documentation for how to disable it.
or
If it's not possible to disable this requirement, then provide documentation on how to setup the C/C++ toolchain, even a mention + a link would be suffcient here.
The text was updated successfully, but these errors were encountered: