[roll] Roll fuchsia [superproject] Roll llvm-project/libc [libc] Build two different static archives libc.a and libm.a under full build. We currently put everything in one single archive libc.a which breaks in certain situations where the compiler drivers expect libm.a also. With this change, we separate out libc.a and libm.a functions as is done conventionally and put them in two different static archives. One will now have to build two targets, `libc` and `libm` which produce `libc.a` and `libm.a` respectively. Under default build, one still builds only one target named `libc` which produces `libllvmlibc.a`. Reviewed By: jhuber6 Differential Revision: https://reviews.llvm.org/D143005 GitOrigin-RevId: 19e12f2b73fcd6004d3d03d8babf2a4b1ec32b98 Original-Revision: f72085ce169868ee998dbc3563de227b3716ff8f Roller-URL: https://ci.chromium.org/b/8790402371851251409 CQ-Do-Not-Cancel-Tryjobs: true Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/795296 Original-Revision: c5d687425caaf49b7a2fd670e056319f922d14c5 Change-Id: I12a504b5a9ce71f64281ae5ef99f0ef27198e1c1
This repository contains Fuchsia's Global Integration manifest files.
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 via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.