[roll] Roll fuchsia [superproject] Roll llvm-project/libc [libc][cmake] error if user disables sanitizers but wants scudo (#123834)

I found this out the hard way...though we don't suggest in our docs setting or
unsetting COMPILER_RT_BUILD_SANITIZERS, I had this explicitly disabled in a
cmake script I was using to setup an llvm-libc based sysroot. While the libc
compiled, hello world failed to link due to missing references to malloc at
link time. Though I had set the cmake variables to opt into using scudo,
apparently explicitly disabling sanitizers will still prevent scudo from being
built... Check for this at configure time and stop the build then.

GitOrigin-RevId: 4a3f7f44084bcdaf947cebf216bac4d55fe18c1e
Original-Revision: 2423bce213c0f89ff3d3855f4429c490a4b711a1
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1191634
Original-Revision: 55fffed18f7aa95a72a358f3798483dd653bd8a1
Change-Id: I36c7c5a56d3fd48364d285d7c13e88474f859a74
1 file changed
tree: d239944fdf372b8d4437099fa6b33477632ac886
  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.