I've not tested the version, but recent commit 45a632ee81c9c5c58309426de5aadbd8dbbba0f5 introduces SYS_mmap2 system call which doesn't exist before 2.3.31. So, should we update the requirement? Is 2.3.31 valid enough?
I'm not sure that we know what the minimum version is these days. If mmap2 is really the only new dependency, adding a workaround is easy enough. Is anybody able to test this?
-- Alexandre Julliard julliard@winehq.org
Hmmm, no answers... It seems to me like crazy project, which nobody on Earth would ever undergo. To promote it from crazy to totally insane I could give a drive to one of my oldies. Like - 486DX - 386DX + 387 / 32MB RAM - 386DX / 4MB RAM with ISA Trident 512KB
(no 386SX / 486SX;) just to see, how deep we can sink with those old ships :-)) I would let Pentium and Pentium MMX docked for being too modern.
So when testing old kernels (Debian distributions) – If that ever compile what else could be interesting? GCC version? Libc version? X version?
How to interpret successful test - compilation? (pre-compiled in VM) - Running winecfg?? - Running MS Paint???
On Wed, May 3, 2017 at 4:25 PM, wylda@volny.cz wrote:
I've not tested the version, but recent commit 45a632ee81c9c5c58309426de5aadbd8dbbba0f5 introduces SYS_mmap2 system call which doesn't exist before 2.3.31. So, should we update the requirement? Is 2.3.31 valid enough?
I'm not sure that we know what the minimum version is these days. If mmap2 is really the only new dependency, adding a workaround is easy enough. Is anybody able to test this?
Hmmm, no answers... It seems to me like crazy project, which nobody on Earth would ever undergo. To promote it from crazy to totally insane I could give a drive to one of my oldies. Like...
Isn't commit https://source.winehq.org/git/wine.git/commitdiff/9f06a197c8c156acf21d8d809c... about this?
Bruno Jesus 00cpxxx@gmail.com writes:
On Wed, May 3, 2017 at 4:25 PM, wylda@volny.cz wrote:
I've not tested the version, but recent commit 45a632ee81c9c5c58309426de5aadbd8dbbba0f5 introduces SYS_mmap2 system call which doesn't exist before 2.3.31. So, should we update the requirement? Is 2.3.31 valid enough?
I'm not sure that we know what the minimum version is these days. If mmap2 is really the only new dependency, adding a workaround is easy enough. Is anybody able to test this?
Hmmm, no answers... It seems to me like crazy project, which nobody on Earth would ever undergo. To promote it from crazy to totally insane I could give a drive to one of my oldies. Like...
Isn't commit https://source.winehq.org/git/wine.git/commitdiff/9f06a197c8c156acf21d8d809c... about this?
For that specific issue, yes. But it would be interesting to find out if there are other issues that we aren't aware of, and whether they would be worth trying to fix. Of course it's low priority, so do it only if that's your idea of fun...
wylda@volny.cz writes:
So when testing old kernels (Debian distributions) – If that ever compile what else could be interesting? GCC version? Libc version? X version?
How to interpret successful test
- compilation? (pre-compiled in VM)
- Running winecfg??
- Running MS Paint???
If you can ever get it to compile, running winecfg is probably good enough as a test. If you run into trouble (as I expect), knowing which version of which component is causing trouble would be interesting.