Skip to content

runtimes: add libgcc-s1, libstdc++6 and zlib1g to the glibc runtimes - #65

Open
snuderl wants to merge 1 commit into
hermeticbuild:mainfrom
snuderl:glibc-jvm-libs
Open

snuderl wants to merge 1 commit into
hermeticbuild:mainfrom
snuderl:glibc-jvm-libs

Conversation

@snuderl

@snuderl snuderl commented Nov 16, 2026

Copy link
Copy Markdown

The glibc runtimes only carried libc6, so common prebuilt toolchains could not start: OpenJDK's launcher (libjli.so) and libzip.so link the system libz, and C++ tools such as rules_java's prebuilt ijar and singlejar link libstdc++ and libgcc_s. This adds the matching packages from the same Ubuntu snapshot and release to all six glibc runtimes (MODULE.bazel only).

Validation: bazel test //src:unit_tests on this branch (211 passed). The resulting runtime image has been running Bazel's remote JDK, rules_java's JavaBuilder/ijar/singlejar and rules_kotlin's compiler in a darwin-actiond serve-vm worker for a large Kotlin/JVM monorepo; tools/e2e.sh vm was not run for this PR.

🤖 Generated with Claude Code

The glibc runtimes only carried libc6, so common prebuilt toolchains could not
start: OpenJDK's launcher (libjli.so) and libzip.so link the system libz, and
C++ tools such as rules_java's prebuilt ijar and singlejar link libstdc++ and
libgcc_s. Add the matching packages from the same Ubuntu snapshot and release
to all six glibc runtimes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant