Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building python binding with bazel on s390x #19232

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gongsu832
Copy link

Changes needed for building python binding with bazel on s390x.

Signed-off-by: Gong Su <gong_su@hotmail.com>
@gongsu832 gongsu832 requested review from a team as code owners November 12, 2024 13:55
@gongsu832 gongsu832 requested review from acozzette and anandolee and removed request for a team November 12, 2024 13:55
@esrauchg esrauchg added the 🅰️ safe for tests Mark a commit as safe to run presubmits over label Nov 12, 2024
@github-actions github-actions bot removed the 🅰️ safe for tests Mark a commit as safe to run presubmits over label Nov 12, 2024
@zhangskz
Copy link
Member

zhangskz commented Nov 13, 2024

We don't currently release or have plans to release python binary wheels for s390x. Is this a request for us to add s390x to our release, or is the purpose of this PR to add these config_settings to enable building for s390x yourself (and if so -- why)?

@gongsu832
Copy link
Author

Hi @zhangskz this is just so that we can build on s390x ourselves. Because protobuf is a dependency for one of our open source project onnx-mlir. Thanks.

copybara-service bot pushed a commit that referenced this pull request Nov 20, 2024
Changes needed for building python binding with bazel on s390x.

Closes #19232

COPYBARA_INTEGRATE_REVIEW=#19232 from gongsu832:python_bazel_s390x 7ed0c48
FUTURE_COPYBARA_INTEGRATE_REVIEW=#19232 from gongsu832:python_bazel_s390x 7ed0c48
PiperOrigin-RevId: 698146211
copybara-service bot pushed a commit that referenced this pull request Nov 21, 2024
Changes needed for building python binding with bazel on s390x.

Closes #19232

COPYBARA_INTEGRATE_REVIEW=#19232 from gongsu832:python_bazel_s390x 7ed0c48
FUTURE_COPYBARA_INTEGRATE_REVIEW=#19232 from gongsu832:python_bazel_s390x 7ed0c48
PiperOrigin-RevId: 698146211
copybara-service bot pushed a commit that referenced this pull request Nov 21, 2024
Changes needed for building python binding with bazel on s390x.

Closes #19232

COPYBARA_INTEGRATE_REVIEW=#19232 from gongsu832:python_bazel_s390x 7ed0c48
FUTURE_COPYBARA_INTEGRATE_REVIEW=#19232 from gongsu832:python_bazel_s390x 7ed0c48
PiperOrigin-RevId: 698146211
@@ -458,6 +479,7 @@ py_dist(
"win64": "310",
"linux-x86_64": "38",
"linux-aarch_64": "38",
"linux-s390x": "38",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gongsu832 Unfortunately I haven't been able to figure out any way to merge this change without breaking our CI, unless I delete this line. Otherwise our build fails because we don't have an appropriate toolchain installed for s390x. Is is still useful to merge the PR without this line? I guess that might still allow you to write your own py_dist() target in a separate repo.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @acozzette thank you very much for trying to merge this PR. Yes it would still be very helpful for us if you could merge without that line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants