None of those are needed by winecfg. They would be needed by some applications, though.
I'm aware of it. But the idea is elsewhere... There are two approaches:
1. i will strictly find the lowest kernel on which i'm able to run winecfg but probably not much more...
2. i will find minimum requirements like pcap-v1.8.1 etc. so, that we can get rid of those generic:
"configure: libpulse development files not found or __too__ __old__"
but user will be given exact version (for Linux and those who care about other OS can do the same). Let's face it - most of programs says for example something like min supported OS: Win7 and higher)
Isn't that "Bug 42478 - Undeclared O_CLOEXEC use in qcap DLL" about this?
Quick googling sugest "O_CLOEXEC (Since Linux 2.6.23)". With commit dfd22fb294c6ce9c3daba311f96ca3b4933d265c shouldn't be min requirements bumped to linux-2.6.23 ??
Sure there is https://github.com/wine-compholio/wine-staging/blob/master/patches/qcap-O_CL...
Then two users having wine-2.7, but with totally different behavior, which is definitely harder to support... Maybe that's OK and then wine probably doesn't need nothing like minimum requirements.
If we don't play on min requirements = it's normal, that some parts of wine do not work. Why there are two kinds of warning?
a) configure: libmpg123 development files not found (or too old), mp3 codec won't be supported.
b) configure: WARNING: libgnutls development files not found, no schannel support.
-
wylda＠volny.cz