z/OS: Fix Bazel bootstrap path handling and JNI loader fallback - #3
Open
harsh-sagar03 wants to merge 7 commits into
Open
z/OS: Fix Bazel bootstrap path handling and JNI loader fallback#3harsh-sagar03 wants to merge 7 commits into
harsh-sagar03 wants to merge 7 commits into
Conversation
Implemented: - Added AutoServiceProcessor to BAZEL_JAVAC_OPTS in buildenv to resolve the unsupported charset error. - Updated unix_cc_configure.bzl to execute scripts through /bin/bash. - Added z/OS enum support in Os.java. Work in progress: - Local rules_python and rules_go overrides. - Initial z/OS support changes in rules_python and rules_go. - working on rules_python and rules_go
harsh-sagar03
requested review from
HarithaIBM,
IgorTodorovskiIBM and
MikeFultonDev
as code owners
August 11, 2026 16:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This continues the ongoing work to get Bazel bootstrapping cleanly on z/OS.
The initial port got us through a number of platform-specific issues around the bootstrap environment, z/OS tooling, and native dependencies. During the latest bootstrap runs, we hit a particularly confusing issue where the generated Bazel binary path was being printed with garbled/corrupted characters. This made it difficult to tell whether Bazel was actually producing the binary or whether the path itself was being mangled.
We went through the bootstrap logs in detail and traced the issue through the Java/runtime environment and the bootstrap path handling.
The path corruption has now been resolved: the Bazel binary path and related output are being produced normally, and the bootstrap has moved past that blocker.
There are still further z/OS-specific build issues to work through, but this PR captures the source changes from this stage of the investigation so the work can be reviewed and built upon.
Generated files and temporary build artifacts are intentionally left out of the changes.