https://bugs.winehq.org/show_bug.cgi?id=50168
--- Comment #7 from Hans Leidekker hans@meelstraat.net --- (In reply to Dmitry Timoshkov from comment #6)
(In reply to Hans Leidekker from comment #5)
(In reply to Dmitry Timoshkov from comment #4)
However it's not trivial to reproduce. I had to run the built binaries on a virtualization server with OpenVZ kernel 2.6.32.
Looks like a variation of bug 49938. The new path uses getrandom() if detected at build time, otherwise it falls back to opening /dev/urandom like we did before.
So your build is probably from a newer system where getrandom() is available and kernel 2.6.32 is certainly too old to support it.
Could we probably try to detect this situation at run-time, and fallback to old behaviour if appropriate?
We could, if we think it's worth it. Note that passing ac_cv_func_getrandom=no would work around the issue. I'm not sure what's reasonable here. Can you still run non-trivial apps on that kernel using a build configured for a modern system?