[roll] Roll fuchsia [bazel] Ensure Clang uses C++ mode for C++ actions.

A new default feature is added to the Bazel C++ host toolchain
configuration to ensure that `clang` runs in C++ mode when
used in C++ compilation actions, and link actions.

Note that Bazel supports C-only compilation actions, which
will not be affected, but does not support C-only link actions,
so the extra flags will be added to C link commands as well.

After this CL is applied, all host GoogleTest tests can be
compiled, and most of them pass:

```
fx set minimal.x64
fx bazel --config=no_sdk @com_google_googletest//...
```

The failing tests are failing to find a Python module at
runtime, so the issue is very likely completely unrelated
to C++ actions.

Original-Bug: 400927814
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1220964
Original-Revision: ef158dd8a770bd49ef46adbdf32425560fbba031
GitOrigin-RevId: 4c0a165fead207dc93117b492ca4a3ee8a4e102c
Change-Id: Ibd0d6b8e843c259b56b589cec418b2dc7b5cd8d5
1 file changed
tree: a4d82605b0b34272a121312d485047939ae4224e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.