-
Notifications
You must be signed in to change notification settings - Fork 709
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
Build fails for Windows ARM64 #1514
Comments
Same here. :( |
#1167 (comment) related |
refer to Try the following in cargo.toml. Install visual studio 2022 and add the following components.
Install LLVM and Strawberry Perl and add them to the environment variable path. |
Thanks @sj6219 . Unfortunately I won't be able to do that as I am using |
@sj6219 thanks for your branch, I have modified it on my side to make it look like the 0.16.20 release, and managed to inject it correctly in all of my dependencies this way. This should work for @mdecimus as well. You can find my branch here: https://github.com/awakecoding/ring/tree/0.16.20_alpha You need to use the following in your Cargo.toml to force-replace the official 0.16.20 release from crates.io with the branch:
You can run "cargo update" and then check that it does get correctly picked up like this:
If you see other ring dependencies listed that don't point to the branch, it'll keep trying to build unpatched versions. The branch requires having clang.exe in the PATH to work properly, but it's preinstalled in most CI environments now. I conditionally patched my cargo.toml file for Windows ARM64 only because the branch doesn't work well for other targets. To test if compilation works, make sure to build executables or shared libraries, otherwise it won't get to throw linker errors. Here's my modified step in GitHub Actions to fix my own build:
You can find the full workflow file for my project here as reference: https://github.com/Devolutions/sspi-rs/blob/master/.github/workflows/nuget.yml |
@awakecoding |
Thanks @awakecoding ! |
@awakecoding You will no longer need a github action. |
do you mean the branch should build cleanly for all platforms, not just Windows ARM64? |
It seems buildable on all platforms. @briansmith knows exactly, but when I tested it on Android, macos, and windows, there was no problem. |
Hi. Thanks for all the interest in this. I think people are mostly interested here in trying to get Rustls working? If so, seems like Rustls people are willing to upgrade to 0.17 when it is released, so I think releasing 0.17 is the most efficient way of moving this forward. Accordingly I'm closing this as a dupe of #1167. |
The `ring` crate doesn't natively support win-arm64 yet. But a fork adds that support [as described here][workaround]. [workaround]: briansmith/ring#1514 (comment)
@awakecoding thanks for #1514 (comment). It seems to work in the simple case. But in a case where Any suggestions? |
The `ring` crate doesn't natively support win-arm64 yet. But a fork adds that support [as described here][workaround]. [workaround]: briansmith/ring#1514 (comment)
The `ring` crate doesn't natively support win-arm64 yet. But a fork adds that support [as described here][workaround]. [workaround]: briansmith/ring#1514 (comment)
The `ring` crate doesn't natively support win-arm64 yet. But a fork adds that support [as described here][workaround]. [workaround]: briansmith/ring#1514 (comment)
The `ring` crate doesn't natively support win-arm64 yet. But a fork adds that support [as described here][workaround]. [workaround]: briansmith/ring#1514 (comment)
Upgrades `aws-config` because `aws-config@0.56` has a dependency on `ring@0.16` [^1] which does not support `aarch64-pc-windows` [^2]. > error: failed to run custom build command for `ring v0.16.20`. Support for `aarch64-pc-windows` was added in `ring@0.17` [^3] which `aws-config@0.57` uses [^4]. Unfortunately, there's a hideous amount of changes between these two version, although no breaking changes are mentioned in the changelog [^5]. Does a maintainer here have a suggestion of what kind of testing we might need to do? [^1]: https://github.com/awslabs/aws-sdk-rust/blob/d212f8dd428e140b8ff414261f6921b2901a7dbc/sdk/aws-config/Cargo.toml#L98-L100 [^2]: briansmith/ring#1514 [^3]: briansmith/ring#1167 (comment) [^4]: https://github.com/awslabs/aws-sdk-rust/blob/511abe92a476c27d1e49758fe54eac0886ecf731/sdk/aws-config/Cargo.toml#L98-L100 [^5]: https://github.com/awslabs/aws-sdk-rust/compare/d212f8d..511abe9
Hi,
I am unable to compile ring using a
windows-2019
orwindows-2022
Github runner image. The CI workflow I used is the same one used in this repository, however the build fails with the following error:To reproduce the error you can run the
ci
workflow in this repository.Thank you.
The text was updated successfully, but these errors were encountered: