RFR: 8339480: Build static-jdk image with a statically linked launcher

[Jiangli Zhou]

On Tue, 3 Sep 2024 12:50:01 GMT, Magnus Ihse Bursie <ihse at openjdk.org> wrote:

> As a prerequisite for Hermetic Java, we need a statically linked `java` launcher. It should behave like the normal, dynamically linked `java` launcher, except that all JDK native libraries should be statically, not dynamically, linked.
> 
> This patch is the first step towards this goal. It will generate a `static-jdk` image with a statically linked launcher. This launcher is missing several native libs, however, and does therefore not behave like a proper dynamic java. One of the reasons for this is that local symbol hiding in static libraries are not implemented yet, which causes symbol clashes when linking all static libraries together. This will be addressed in an upcoming patch. 
> 
> All changes in the `src` directory are copied from, or inspired by, changes made in [the hermetic-java-runtime branch in Project Leyden](https://github.com/openjdk/leyden/tree/hermetic-java-runtime).

src/java.base/unix/native/libjli/java_md.c line 509:

> 507: 
> 508:     if (GetApplicationHome(path, pathsize)) {
> 509:         if (JLI_IsStaticallyLinked()) {

`GetJREPath()` does not need to be called for the static case. Any reason why this path is executed for static mode?

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/20837#discussion_r1744642315