add_custom_libcxx uses the just built compiler and installs the
built libc++, e.g. for testing, neither of which is desirable in
case of Fuzzer where the libc++ should be built using the host
compiler and it's only linked into the libFuzzer and should never
be installed. This change introduces add_internal_libcxx which
allows building such version of libc++.
Details
Details
- Reviewers
vitalybuka EricWF - Commits
- rG066e4bf88846: Reland "[Fuzzer] Parametrize add_custom_libcxx"
rG94e67be18729: [Fuzzer] Parametrize add_custom_libcxx
rCRT323054: Reland "[Fuzzer] Parametrize add_custom_libcxx"
rL323054: Reland "[Fuzzer] Parametrize add_custom_libcxx"
rCRT323032: [Fuzzer] Parametrize add_custom_libcxx
rL323032: [Fuzzer] Parametrize add_custom_libcxx
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
cmake/Modules/AddCompilerRT.cmake | ||
---|---|---|
511 ↗ | (On Diff #130744) | maybe we can just call here add_internal_libcxx( |
Comment Actions
Thanks for getting to this so quickly. However, it still fails when cross compiling. I'm trying to debug it now.
Comment Actions
Looks like the problem is that you aren't passing all the required parameters expected when cross compiling, e.g., CMAKE_SYSROOT, etc.
Doesn't look like any other active code is using these macros. I'm happy to test, but plan to disable the fuzzer for the time being.
Comment Actions
Thanks for adding CMAKE_SYSROOT, but it's still not passing all the required variables. I'll just disable it for now and followup later with a full list in a separate patch.
Thanks again...