-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
When building with --enable-asan, a runtime dependency on libasan.so is added to every library and executable in the JDK. The version of this library is tightly bound to the version of the compiler (GCC). When building using a devkit/sysroot, or when building on one machine to run tests on another, fulfilling this runtime dependency can be tricky, resulting in an error like this:
.../build/linux-aarch64/jdk/bin/javac: error while loading shared libraries: libasan.so.8: cannot open shared object file: No such file or directory
One way to address this would be to optionally bundle the libasan.so from the system/sysroot/devkit into the JDK image so that the correct version is available at runtime. This would be similar to how libffi is can be bundled when building zero.
.../build/linux-aarch64/jdk/bin/javac: error while loading shared libraries: libasan.so.8: cannot open shared object file: No such file or directory
One way to address this would be to optionally bundle the libasan.so from the system/sysroot/devkit into the JDK image so that the correct version is available at runtime. This would be similar to how libffi is can be bundled when building zero.