With such a config_setting, you would not set force_pic, but make it possible for e.g. selects to depend on its value. Could you try again with:

bazel build //:jazzer --force_pic

This gives me:

❯ file bazel-bin/driver/jazzer_driver
bazel-bin/driver/jazzer_driver: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[xxHash]=18d2f7b0ad33a53e, with debug_info, not stripped

So, even after doing force_pic, the binary still didn't work, the error message read:

CANNOT LINK EXECUTABLE "./jazzer": library "libdl.so.2" not found: needed by main executable

I tried following bazel instructions, and ran this command to try building via the NDK (after setting up prerequisites):

./bazelisk-linux-amd64 build //:jazzer_release --force_pic --crosstool_top=@androidndk//:default_crosstool --cpu=x86_64 --host_crosstool_top=@bazel_tools//tools/cpp:toolchain

The resulting binary gave the same errors as without using the NDK.

I also tried to gather the required libraries for my android fuzz target on the host to try and see if I can fuzz it using jazzer locally on x86 linux, but got this error:

Java Exception: java.lang.UnsatisfiedLinkError: 'boolean android.util.Log.isLoggable(java.lang.String, int)'

It's a native method compiled as the target libandroid_runtime, I tried to make it available to the binary at runtime by putting libandroid_runtime.so in the same directory as my compiled fuzz target .class, and trying to provide the path to it as:

Djava.library.path="./lib"

where the .so files were added to the ./lib directory.
But still ran into the same UnsatisfiedLinkError.

So, even after doing force_pic, the binary still didn't work, the error message read:

CANNOT LINK EXECUTABLE "./jazzer": library "libdl.so.2" not found: needed by main executable

Did you try this with current main? We dropped the dependency on libdl in 554bfe4.

It's a native method compiled as the target libandroid_runtime, I tried to make it available to the binary at runtime by putting libandroid_runtime.so in the same directory as my compiled fuzz target .class, and trying to provide the path to it as:

Djava.library.path="./lib"

where the .so files were added to the ./lib directory. But still ran into the same UnsatisfiedLinkError.

How did you pass this argument to Jazzer? Since Jazzer launches its own JVM, you might have to pass it via --jvm_args. Alternatively, if this is available on Android, you could add ./lib (or ideally an absolute path) to LD_LIBRARY_PATH or even LD_PRELOAD the native library.

1. Reset my local repo to main, but still got the libdl.so.2 not found error.

2. Even after adding ./lib to LD_LIBRARY_PATH, still got UnsatisfiedLinkError.

3. I tried running jazzer with --jvm_args=-Djava.library.path= ".../lib/libandroid_runtime.so". It showed me ./jazzer: Running 1 inputs 1 time(s) each. Running: ...s/lib/libandroid_runtime.so, but still got the UnsatisfiedLinkError eventually.

4. Adding the library's absolute path to LD_PRELOAD also didn't work.

I think the 2 most promising ideas may be using robolectric alongside jazzer, or building jazzer for android. Still a bit surprised why using the ndk to build jazzer didn't work previously.