diff options
| author | Fabian Meumertzheim <meumertzheim@code-intelligence.com> | 2021-08-04 10:13:18 +0200 |
|---|---|---|
| committer | Fabian Meumertzheim <fabian@meumertzhe.im> | 2021-08-09 09:36:03 +0200 |
| commit | 89285d8f3d3653b37aa9165b05ddbfec50141198 (patch) | |
| tree | ac717d760e5a286729dece0cda4b90e99a1e6ac5 /README.md | |
| parent | 3282049bdf62d053a7ac9a0157ca3ef0f0c4ec27 (diff) | |
| download | jazzer-api-89285d8f3d3653b37aa9165b05ddbfec50141198.tar.gz | |
Use an LLVM Bazel toolchain in the CI
The toolchain is only enabled in the CI by default as users should use
the same compiler toolchain for compiling the Jazzer driver as they use
to compile their JNI libraries. However, if they are only interested in
fuzzing pure Java libraries, they can pass --config=ci on the CLI to use
the toolchain, which greatly simplifies the build on macOS.
A significant complication arises because the ASan runtime library can't
be linked statically on macOS. To make the tests pass, it needs to be
exported from the toolchain and the driver has to conditionally depend
on it explicitly.
A further patch to the toolchain is required to ensure compatibility
with Ubuntu 21.04.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -84,6 +84,9 @@ Target //:jazzer_release up-to-date: This will print the path of a `jazzer_release.tar.gz` archive that contains the same binaries that would be part of a release. +The build may fail with the clang shipped with Xcode. If you encounter issues during the build, add `--config=toolchain` +right after `run` or `build` in the `bazelisk` commands above to use a checked-in toolchain that is known to work. + ### Using the provided binaries Binary releases are available under [Releases](https://github.com/CodeIntelligenceTesting/jazzer/releases) and are built |