-
Notifications
You must be signed in to change notification settings - Fork 26
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
Is the ARM runner provided by osuosl? #84
Comments
No. I got access to their aarch64 openstack, but I couldn't get it to work out either technically or licensing-wise to be able to run Windows on it. I wound up with the MS Dev Kit instead, which has Hyper-V. |
So, I think you/we should tell them to remove MSYS2 from that list. |
We couldn't make use of it and from what I see it's not active, see msys2/msys2-autobuild#84 (comment)
I've filed a PR for this: osuosl/osuosl-pelican#585 |
I have already sent them an email about it, They replied by asking @jeremyd2019 if he wants to.
|
Maybe offtopic, https://github.blog/changelog/2024-03-04-github-actions58-larger-runners-windows-11-beta/ they now have beta Win11 images, so I guess they have figured out the licensing, at least for themselves. |
We didn't get a final answer from either sides. |
We couldn't make use of it and from what I see it's not active, see msys2/msys2-autobuild#84 (comment)
Can MSYS2 run in Wine? |
It has some issues msys2/MSYS2-packages#682 |
Linaro offers a docker image with prebuilt wine-arm64: https://linaro.org/blog/emulate-windows-on-arm/ I have pulled the image locally, and it is Debian on AMD64, with Wine ARM64 emulated by QEMU. So in theory we can install both Wine AMD64 and Wine ARM64. The AMD64 Wine run MSYS2 and the ARM64 Wine can run CLANGARM64 tools. |
There is a wine fork that in theory allows running cygwin: https://gitlab.winehq.org/jhol/wine/-/commits/msys2-hacks-17 (note that the branch name changes on each rebase) |
@jeremyd2019 In https://osuosl.org/services/aarch64/current-projects/ they metion MSYS2.
Is it true. Just to make sure.
The text was updated successfully, but these errors were encountered: