http://bugs.winehq.org/show_bug.cgi?id=14422
--- Comment #8 from max@veneto.com 2008-07-18 13:49:17 --- (In reply to comment #7)
Created an attachment (id=14836)
--> (http://bugs.winehq.org/attachment.cgi?id=14836) [details]
error log - installing winetricks msxml3
I recompiled last wine (in gentoo it is wine-9999) sh /tmp/winetricks corefonts installed OK sh /tmp/winetricks dotnet20 installed OK
But sh /tmp/winetricks msxml3 get stuck eat up all cpu, log is atatched.
Yep, found too... then updated to newest git and the msxml3 error is gone. BUT... the gdiplus is there. After launching autocad 3-4 times it starts up, but on exit it hangs and leaves with a gdiplus error again.
Well, I lost half a day to find regression for msxml3... and now it's gone. My "old" wine prefix with autocad still works well, so I guess it's again a regression in setup side... as just the newly installed autocad has problems.
The problem seems the same as using dotnet1.1, so I guess some patch broke net setup. I'm afraid that to locate the bad patch will be quite time expensive, as I can only reproduce it wiping .wine, reinstalling dotnet20 (and other stuffs, along msxml3 which is broken somewhere in the middle), reinstall autocad, run it, bisect, and redo all stuff. About 20 minutes per run, so IMHO 1 full day at least to locate the bad commit....
Shouldn't we have some tests for dotnet ??? We're speaking about having one-testcase-per-patch, even for very simple and straightforward ones, but in few days we've got msxml3 setup broken (and now ok again...) and (afaik...) dotnet20 also broken.
Max