Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JDK-8247589 was backported to OpenJDK 11.0.16 upstream (slated for a July 19, 2022 GA) in openjdk/jdk11u-dev#910, but it appears to have been backported to Adoptium/Temurin sooner than that in adoptium/jdk11u#7 and is already shipping in Temurin 11.0.15. As a result it is no longer necessary to include
glibc
.Testing done
Built this Docker image. Verified that
java
is not linking againstglibc
:Installed Jenkins and verified there were no errors or stack traces printed in the console log. Then went to the script console and induced a crash:
Examining the resulting HotSpot error file, I see that
musl
is loaded in the process address space:Additionally I see the following strings:
The former indicates that https://github.com/adoptium/jdk11u/blob/982989d67b04ab2c4047c31acbf02e82b55c3072/src/hotspot/os/linux/os_linux.cpp#L626= must have been executed, which implies
MUSL_LIBC
must have been defined when compiling the software.