Build gRPC without c-ares (#32649)

The Bazel client only connects to the server via `127.0.0.1` or `[::1]` (enforced in `BlazeServer::TryConnect`), so it never needs DNS resolution. For IP literals, gRPC doesn't consult the resolver anyway. This PR sets `--define=grpc_no_ares=true` so that gRPC is built with `GRPC_ARES=0` and c-ares drops out of the build graph of `//src:bazel` entirely, which also removes the c-ares compiler warnings (unused function/variable, deprecated c-ares APIs used by gRPC). Since c-ares is no longer built, its version override and its entry in the distribution archive are removed as well. envoy_api, googleapis-grpc-java, googleapis-java, opencensus-cpp, rules_fuzzing and toml.bzl are also dropped from the distribution archive, since a build of Bazel no longer fetches them.

Closes #32649

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/32649 from fmeum:grpc-no-ares b7a25c9cd50ec71be0174f0e22f889315d34e905
PiperOrigin-RevId: 1023219360
Change-Id: I5edffc42d21c6de4703f4203268e1e83b41be115
5 files changed
tree: a164bfd53eb4eebf84ab6be1e5475e066bb33e56
  1. .bazelci/
  2. .devcontainer/
  3. .gemini/
  4. .github/
  5. docs/
  6. examples/
  7. scripts/
  8. src/
  9. third_party/
  10. tools/
  11. .bazelrc
  12. .bazelversion
  13. .gitattributes
  14. .gitignore
  15. AGENTS.md
  16. AUTHORS
  17. bazel_downloader.cfg
  18. BUILD
  19. CHANGELOG.md
  20. CODE_OF_CONDUCT.md
  21. CODEOWNERS
  22. combine_distfiles.py
  23. combine_distfiles_to_tar.sh
  24. compile.sh
  25. CONTRIBUTING.md
  26. CONTRIBUTORS
  27. distdir.bzl
  28. extensions.bzl
  29. LICENSE
  30. maven_install.json
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. oneversion_allowlist.csv
  34. oneversion_allowlist_for_tests.csv
  35. pyproject.toml
  36. README.md
  37. repositories.bzl
  38. requirements.txt
  39. SECURITY.md
  40. verify_module_bazel_lock.sh
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status