If winecfg runs, that should be good enough. Optional packages can be backported if necessary.
OK, then I will concentrate on min kernel version :)
Currently I build wine-2.8 on machine with: * Linux-v2.4.27-3-386 * gcc-v3.3.5 * libc6-v2.3.2
There were few failures which I overcome by not building these components: * dwrite * winealsa.drv * wmvcore * ws2_32 * programs/winhlp32
When I run winecfg, I got:
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination. Please upgrade to a glibc with NPTL support.
Should I interpret that message, that: 1. NPTL is required 2. I should use glibc-2.2 or lower
If 1) that's probably end of game per https://lwn.net/Articles/10465/ * "- The 2.5.36 kernel or above must be installed and used." * "The current snapshot for glibc 2.3 (or glibc 2.3 when released) is necessary." * "The general compiler requirement for glibc is at least gcc 3.2."
So for further steps 1) or 2) ?
wmvcore and winhlp32 look like a real bugs. Others failures can be probably be solved by using newer components. I can open bugreports, if anyone is interested.
Regards, W.
wylda@volny.cz writes:
When I run winecfg, I got:
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination. Please upgrade to a glibc with NPTL support.
Should I interpret that message, that:
- NPTL is required
- I should use glibc-2.2 or lower
If 1) that's probably end of game per https://lwn.net/Articles/10465/
- "- The 2.5.36 kernel or above must be installed and used."
- "The current snapshot for glibc 2.3 (or glibc 2.3 when released) is necessary."
- "The general compiler requirement for glibc is at least gcc 3.2."
So for further steps 1) or 2) ?
A glibc using TLS might still work without NPTL, though that may require glibc 2.3 anyway. Note that the above requirements are for building glibc, not running it. The NPTL support was backported to older kernels IIRC.