-
Notifications
You must be signed in to change notification settings - Fork 90
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
[Bug]: hangover-wine 9.20.1: wine-mono installation failed #1309
Comments
Well, I am not an expert. It seems to me that the problem is the experimental implementation of 64-bit. Initially it looks like Mono is installing however, not all data is saved in the registers? Generally, in Wine Uninstaller, Mono appears to me, however, when I try to run the .Net application, it pops up information that Wine Mono is not installed. @AndreRH |
I'll have a look. Which .net app did you use for testing? |
I write a simple Hello World code
It works using Wine on Debian (and normal Mono) but not in Hangover Here you have a source code and compiled version. Wine on Debian:
Hangover Uninstaller list (It looks like Wine Mono is installed, however ...): Hangover on Termux (without X11, just using SSH - but should work): |
It's complicated. I can make mono be autoinstalled in hangover and better detected, but that won't help with your .net app, which says is "x86". It will be detected as .net only and treated as a aarch64 binary. But it would need to be treated as a arm64ec binary to be able to load a x86_64 mono library. |
I would perhaps stay on topic for the time being and keep an eye on whether Wine Mono for ARM will be developed, since .Net applications are independent of processor architecture. |
Problem description
In the new
hangover-wine 9.20.1
, I successfully installedNotepad++ 32-bit
,but the
wine-mono
installation keeps failing.Is there something I might be missing?
@licy183 @IntinteDAO
What steps will reproduce the bug?
What is the expected behavior?
No response
System information
termux-info:
The text was updated successfully, but these errors were encountered: