https://bugs.winehq.org/show_bug.cgi?id=47224
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #9 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Gcenx from comment #8)
While the mount issue is resolved in Wine-4.10 Winehq packages I would like confirmation that mingw was added into the builder or not. As too many bugs are happening when building without mingw.
I don't maintain the macOS packages, so I can't say definitively what was done in the builder. What I can say is that after extracting the macOS "portable" packages for 4.9 and 4.10, the /usr/lib/wine subdirectory for 4.10 includes many files with just a dll extension that in 4.9 had a dll.so extension, and the file command identifies those dll files as "PE32 executable (DLL) (console) Intel 80386, for MS Windows" whereas the corresponding dll.so files in 4.9 return "Mach-O i386 bundle, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL>". So clearly something has changed in the build process.
Also while the bug was fixed within the Winehq packages I was also told from someone who also builds wine regularly they still get the mounting issue when passing —without-mingw.
I haven’t had chance to test building —without-mingw myself yet due to needing my laptop today
This bug is about the WineHQ packages, and those have been reported fixed. Problems that occur when you build Wine yourself without mingw should be reported separately as Wine bugs, not Packaging bugs.