-
Notifications
You must be signed in to change notification settings - Fork 704
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
Add support for aarch64-pc-windows-msvc #1614
Comments
thread 'main' panicked at '"C:\\Users\\Administrator\\.cargo\\registry\\src\\index.crates.io-6f17d22bba15001f\\ring-0.16.20\\pregenerated\\aesv8-armx-linux64.obj": Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }', C:\Users\Administrator\.cargo\registry\src\index.crates.io-6f17d22bba15001f\ring-0.16.20\build.rs:769:10
Also fails on aarch64-pc-windows-gnullvm with an error about not finding a linux object file:
|
It actually looks like this may have been done on main, but there just hasn't been a release with such support yet. See #1339 (comment) |
Me too, build failed. So painful.......... |
did you manage to solve it ? @mobeicanyue |
no, i said i build my program failed because of ring do not support arm Windows |
Same here. Fails for aarch64-pc-windows-msvc
|
Hi everyone, Quite some folks have managed to patch 0.16.x to build on aarch64-pc-windows-msvc: #1554 I’d suggest to use one of those forks for now (1Password’s one might be a good choice). |
Why not merge it and release 0.16.21😂😂,not familiar with path dependencies |
@mobeicanyue I’m not a maintainer here 🤷♂️ I’m blocked on a bunch of projects myself by this. I believe @briansmith’s main concern about the existing PR (the one that I’ve linked) is the amount of changes suggested. If we could use 1Password’s branch mentioned there by @complexspaces to open a new PR, maybe that could be an easier change for @briansmith. Or maybe @svenpaulsen would prefer to update his PR? I believe there’s an unanswered question from @briansmith there. |
Any status on this? Not being able to work with a lot of libraries on Windows ARM is pretty big show stopper since major libraries like Rustls rely on Ring... |
Any update? |
Hi friends, I have just returned from a long break. I have spent most of my ring-related time working on big-picture issues (funding and governance) for the project going forward. I understand that this is an issue that is blocking some projects from moving forward and it is tantalizingly close to being done. I am also frustrated about the situation and I'm actively working on a solution. Stay tuned. |
OK, friends, I think this is happening now. Could anybody volunteer some solution for running the tests on ARM64 Windows in GitHub Actions? The current story doesn't look good from reading actions/runner-images#768 and actions/runner-images#6175 and actions/runner-images#7507 (comment). When we originally did the Windows Aarch64 work, I used a Surface Pro X over SSH to test this. This is hardly a sustainable solution for a production release though. My understanding is that I could set something up on Azure to build a Windows ARM64 private builder. But...I don't know how and I don't really want to spend time to figure it out. |
Also, if you have the ability to test the main branch on Aarch64 Windows (building ring from Git requires installing Perl; sorry in advance), it would be great if you could comment on #1595 about your experience with that change. Presumably it is good and it works. If some (non-anonymous) people can verify it works I can merge that PR presumptively until I can dig out my Surface Pro X to verify it. Regardless, I will need to dig out the Surface Pro X for the verification before doing the final 0.17 release. |
Can we use |
Probably because the version is not satisfied, I cannot test by add crate patch. |
First of all, this is a duplicate of issue #1167, which I didn't even notice until now. Regardless, as I said in that issue: Closing this as completed with the ring 0.17.0 release. I was able to build and test both natively on ARM64 Windows and cross-compile from x86_64 Windows. PR #1691 clarifies the documentation. I also filed issue #882 for cc-rs to help make this easier so that modifying %PATH% will no longer be required in the future. Thanks for all the help here! I really appreciate it. |
Hi
Currently, it looks like there is no support for aarch64-pc-windows-msvc
PR: mokeyish/smartdns-rs#152
It failed to build in my CI task. https://github.com/mokeyish/smartdns-rs/actions/runs/6280532933/job/17057868305?pr=152
The text was updated successfully, but these errors were encountered: