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

boringssl still fails on debian s390x #16

Open
rogers0 opened this issue Jun 12, 2022 · 2 comments
Open

boringssl still fails on debian s390x #16

rogers0 opened this issue Jun 12, 2022 · 2 comments

Comments

@rogers0
Copy link

rogers0 commented Jun 12, 2022

I tried to build and run tests for boringssl on debian s390x porterbox.
Seems the patch you provided was already upstreamed:

So there's no need to patch anymore.
However, the tests still fail:

  • compiler_test
  • crypto_test
  • ssl_test

docs from boringssl mentioned it only supports little-endian architectures. I guess that's why the tests failed.

So I want to double confirm with you

  • have you run test for boringssl?
  • how did you support big-endian for boringssl?

Thank you!

@aborkar-ibm
Copy link
Contributor

Hello,

We have built and run the test cases for boringssl. The test cases you mention do pass for us on Ubuntu18.x at the time we work on it.
Please note that we do not maintain boring ssl.
The changes done are on an older commit. The script does build the source at https://github.com/linux-on-ibm-z/boringssl/tree/patch-s390x-Jan2021
We have made minimum changes required to build and test boringssl in this branch to allow the package that depends on it to build. It's not a complete port or support of BE.

@rogers0
Copy link
Author

rogers0 commented Jun 13, 2022

@aborkar-ibm

Thanks for your prompting feedback!
Understood the current status.

Hope you can check latest from boringssl soon, and maybe resolve some issues for the tests sometime later.

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

No branches or pull requests

2 participants