https://bugs.winehq.org/show_bug.cgi?id=46981 --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- (In reply to Andy P from comment #4)
Thanks Austin.
Might I ask which wine build # / branch you were using?
I was mostly testing with wine-4.0. There were some regressions in newer wine (e.g., bug 47436). That should be fixed with newer versions (though I've seen some reports there may be issues related to using/not using mingw, so I wanted to stick to a version that I knew worked with at least 32-bit dotnet (and that I already had 64-bit binaries built for).
How did you verify 4.0 and 4.5 worked? Did you run a sample app or ntfx_verify?
I'm not sure what you mean by ntfx_verify. Do you mean dotnet_verifier? In this case I was running ./tests/winetricks-test, with 32/64 bit wine with my testing branch (https://github.com/austin987/winetricks/tree/dotnet-binaries2). The branch runs dotnet_verifier (already in winetricks) but also binaries I built with mcs (as I said in comment #3): #32-bit: austin(a)laptop ~/src/winetricks (dotnet-binaries2) $ export WINE=/opt/oldwine/wine-4.0/bin/wine austin(a)laptop ~/src/winetricks (dotnet-binaries2) $ time ./tests/winetricks-test dotnet #64-bit: austin(a)laptop ~/src/winetricks (dotnet-binaries2) $ export WINE=/opt/oldwow64/wine-4.0/bin/wine64
Also any details on how 4.6 and above failed? Internal error in clr.dll?
Yep, similar backtraces to what I have in original comment. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.