https://bugs.winehq.org/show_bug.cgi?id=37697
--- Comment #16 from Alon Levy alon@pobox.com --- (In reply to Anastasius Focht from comment #15)
Hello again,
to clarify at least - even counting in the possibility that you somehow still used Wine-staging for running the installer ...
The 'comctl32' runtime crash during compilation action is gone when you run the app with Wine-Staging (formerly 'compholio')?
Sorry for confusing, I'll try to be clearer:
The crash happens sometimes, I do not have a clear reproducer, it happens during build (perhaps actually when it is done, like I said, I don't know).
I don't have a self built version of wine-staging, I've used it previously from the fedora builds, that's it.
Regarding the patchset - my bad, I assumed they were all pushed, now that I searched for the actualy implementation it is as you said, not on master.
So I still have no idea why it is working, unless like you say I somehow have kernel32.dll not from master. Oh well, I'll leave it be for now from ELACKOFTIME.
In that case it would be useful to know which patchset fixed it. Unfortunately I don't have that much time to do that, also it's not very challenging :)
The basic idea is that you apply staging-provided patchsets on top of the Wine source tree (source tarball or better GIT), one-by-one (first named pipe stuff, next user32/comctl32 related patches), rebuild, run/verify.
There is a 'patches/patchinstall.sh' script which enables you to do that (default action would be '--all' which is not helpful in this case).
Thanks, I'll keep that in mind. But I don't intend to try staging for now, unless I run into any problems I must fix, since the current version is stable enough for me - this problem is severe but infrequent.
Regards
Alon