This RFE is inspired by the discussion in https://github.com/openjdk/jdk/pull/24103 comment thread (https://github.com/openjdk/jdk/pull/24103#issuecomment-2735014436):
To test the cases of using custom native launcher executable to launch VM on static JDK, we need to create tests that build testing native launcher executables statically linked with needed JDK/VM static libraries. The existing tests listed inJDK-8352276 are not suitable for the testing purpose.
As the testing native launcher executable needs statically linking with the JDK/VM static libraries, e.g. libjvm.a, some build infrastructure work is also needed to enabling building the static-libs to provide the JDK/VM static libraries when creating the test image. Instead of building static-libs by default when building test image, it's probably worth looking into adding a new test-static-image target to build test natives requiring statically linking with JDK/VM.
To test the cases of using custom native launcher executable to launch VM on static JDK, we need to create tests that build testing native launcher executables statically linked with needed JDK/VM static libraries. The existing tests listed in
As the testing native launcher executable needs statically linking with the JDK/VM static libraries, e.g. libjvm.a, some build infrastructure work is also needed to enabling building the static-libs to provide the JDK/VM static libraries when creating the test image. Instead of building static-libs by default when building test image, it's probably worth looking into adding a new test-static-image target to build test natives requiring statically linking with JDK/VM.
- relates to
-
JDK-8352276 Skip jtreg tests using native executable with libjvm.so/libjli.so dependencies on static JDK
-
- Resolved
-
-
JDK-8303796 Optionally build fully statically linked JDK image
-
- Open
-