I found that recent GIT changes makes msvcp100.dll crash with: --- 0009:err:heap:HEAP_GetPtr Invalid heap (nil)! 0009:err:heap:HEAP_GetPtr Invalid heap (nil)! 0009:err:module:LdrInitializeThunk "msvcp100.dll" failed to initialize, aborting --- when compiling wine with the --without-mingw option.
If i compile with default (ie. mingw enabled), seemingly things work. Is this intentional, and mingw is now "required" for wine compile? Or would i perhaps have gotten away with the it if jumping through some hoops with dll-overrides and winetricks usage?
Git 0d175fe861826d4cf756291bd43404aba065cec6 and older seems to work as before tho.
Sveinar
Sveinar Søpler cybermax@dexter.no writes:
I found that recent GIT changes makes msvcp100.dll crash with:
0009:err:heap:HEAP_GetPtr Invalid heap (nil)! 0009:err:heap:HEAP_GetPtr Invalid heap (nil)! 0009:err:module:LdrInitializeThunk "msvcp100.dll" failed to initialize, aborting
when compiling wine with the --without-mingw option.
If i compile with default (ie. mingw enabled), seemingly things work. Is this intentional, and mingw is now "required" for wine compile?
No, but evidently the without-mingw case gets less testing ;-)
Please file bugs when you encounter issues. For this specific one, there's already https://bugs.winehq.org/show_bug.cgi?id=47238
Ok. Thanks.
I thought i would probe the mailinglist before posting a bug, since for all i know it could be some new intended behavior. Since i need sleep someone postet that bug before i read the answer :)
Sveinar
----- On May 21, 2019, at 11:41 AM, Alexandre Julliard julliard@winehq.org wrote:
No, but evidently the without-mingw case gets less testing ;-)
Please file bugs when you encounter issues. For this specific one, there's already https://bugs.winehq.org/show_bug.cgi?id=47238
-- Alexandre Julliard julliard@winehq.org
-
Alexandre Julliard -
Sveinar Søpler