Fix compile-time issues for Bazel on z/OS - #2
Conversation
🤖 Augment PR SummaryReview Notes (unanchored due to PR size/API limits):
🤖 Was this summary useful? React with 👍 or 👎 |
| @@ -1 +0,0 @@ | |||
| 7.1.1 | |||
There was a problem hiding this comment.
.bazelci/.bazelversion Removing the pinned Bazel version may make builds less reproducible for contributors/tools that rely on bazelisk/.bazelversion pinning. If the intent is to drop CI/dev scaffolding, consider confirming there�[39m�[0m�[0m�[0m�[39m�[0m isn�[39m�[0m�[0m�[0m�[39m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[0m�[0m�[39m�[0m�[39m�[0m is an alternative pin/versioning mechanism for the z/OS port build.
Severity: low
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
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
… and .d newline issue
Updated the README to enhance clarity and structure for building Bazel on z/OS, including detailed steps for cloning the repository, tagging binary files, configuring toolchains, and building. Signed-off-by: RohiniShankari <136949412+RohiniShankari@users.noreply.github.com>
Summary
Notes