Emerging win4lin-sources-2.4.26-r6 ends up with an error like: mki24.c: In function `mkia_free_ldt': mki24.c:270: error: structure has no member named `segments' mki24.c: In function `mkia_alloc_ldt': mki24.c:445: error: structure has no member named `segments' mki24.c: In function `mkia_set_gdt_entry': mki24.c:812: error: structure has no member named `segments' mki24.c: In function `mkia_set_ldt_entry': mki24.c:829: error: structure has no member named `segments' mki24.c:831: error: structure has no member named `segments' mki24.c:834: error: structure has no member named `segments' mki24.c: In function `mkia_getparm': mki24.c:953: error: structure has no member named `segments' mki24.c: In function `mkia_set_private_ldt': mki24.c:1114: error: structure has no member named `segments' mki24.c:1126: error: structure has no member named `segments' mki24.c:1140: error: structure has no member named `segments' make[1]: *** [mki.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.26-win4lin-r6/arch/i386/mki-adapter' make: *** [_mod_arch/i386/mki-adapter] Error 2 The reason is that the mki-adaptor patch which I pick up off my local mirror is incompatible with recent 2.4.x kernels, even though it appears to apply correctly. Apparently with the 2.4 series, Netraverse would silenty update the mki-adaptor patch without changing the filename. I suggest that the latest mki-adaptor patch from http://www.netraverse.com/member/downloads/files/mki-adapter.patch should be placed on the mirrors as mki-adaptor-2.4.26.patch (or similar), and the gs-sources-2.4.26 ebuild should be updated accordingly. Reproducible: Always Steps to Reproduce:
Is converting to 2.6 kernel an option for you? There are working 2.6 win4lin ebuilds.
I got the 2.4 kernel working with win4lin as per these instructions. Actually win4lin is the only thing stopping me from moving that box to 2.6 --- it has a version 4 win4lin, which is not compatible with kernel 2.6. To run kernel 2.6, someone would need to buy a license for win4lin 5.
The mirrors and digests have been updated; please reopen this bug if you still have any issues...
