Cannot compile app-emulation/vmware-modules-1.0.0.25-r1 with gentoo-sources-2.6.36-r5. Fix is to upgrade to app-emulation/vmware-modules-1.0.0.25-r2. Please stabilise this revision asap.
Does not compile for gentoo-sources-2.6.37 either. For further information how to avoid the error ("error: implicit declaration of function ‘init_MUTEX’"), please check http://communities.vmware.com/message/1675554?tstart=0
(In reply to comment #1) > Does not compile for gentoo-sources-2.6.37 either. For further information how > to avoid the error ("error: implicit declaration of function > ‘init_MUTEX’"), please check > http://communities.vmware.com/message/1675554?tstart=0 Is this with app-emulation/vmware-modules-1.0.0.25-r1?
> Is this with app-emulation/vmware-modules-1.0.0.25-r1? > Yes, emerging fails with the same error message.
(In reply to comment #3) > > Is this with app-emulation/vmware-modules-1.0.0.25-r1? > > > > Yes, emerging fails with the same error message. OK I'm hoping they'll stabilise app-emulation/vmware-modules-1.0.0.25-r2 soon and that will hopefully sort it for 2.6.36 and 2.6.37. I will be testing 2.6.37 with -r2 within the next few days. In the meantime, -r2 definitely does work with 2.6.36.
Created attachment 259581 [details, diff] patch for 2.6.37 I wrote a simple patch for 2.6.37-gentoo . I had to reconfigure vmware-networking. (emerge --config vmware-workstation) (for me working :) )
Thanks for that, you just beat me to it! I can confirm that vmware-modules-1.0.0.25-r2 needs the patch to build under 2.6.37!
(In reply to comment #6) > Thanks for that, you just beat me to it! I can confirm that > vmware-modules-1.0.0.25-r2 needs the patch to build under 2.6.37! > Likewise, I confirm the patch works for me on 2.6.37. Thanks!
thank y'all. patch is in the portage. I'll create a stabilization bug along with workstation 6.5.5 in a short while.
Unfortunately vmware-modules-1.0.0.25-r3 does not compile on my machine: 2.6.37-gentoo-sources, amd64
AHA, the error involves missing "unlock_kernel" and "lock_kernel" symbols. Seems that I need to recompile with BKL support :-P. Perhaps the ebuild should check for this and give a reasonable message? (In reply to comment #9) > Unfortunately vmware-modules-1.0.0.25-r3 does not compile on my machine: > > 2.6.37-gentoo-sources, amd64 >
Hmm, is there a reason to respect BKL? Praised as one of the biggest improvements of 2.6.37 it shouldn't be necessary to activate BKL.
(In reply to comment #10) > AHA, the error involves missing "unlock_kernel" and "lock_kernel" symbols. > Seems that I need to recompile with BKL support :-P. You need to enable CONFIG_LOCK_KERNEL (not CONFIG_BLK) https://bugs.gentoo.org/show_bug.cgi?id=350739#c8
Seems to work just fine now that vmware-modules has gone stable.
(In reply to comment #12) > (In reply to comment #10) > > AHA, the error involves missing "unlock_kernel" and "lock_kernel" symbols. > > Seems that I need to recompile with BKL support :-P. > > You need to enable CONFIG_LOCK_KERNEL (not CONFIG_BLK) > https://bugs.gentoo.org/show_bug.cgi?id=350739#c8 I know I'm going to sound stupid, but I can't seem to find where to set CONFIG_LOCK_KERNEL. I can't see it under: "General setup" nor under: "Processor type and features" I probably turned off something else required for it to display but I haven't a clue as to what. Can someone please give me some guidance? Thanks!
Oops! I forgot to note I'm using vanilla-sources-2.6.37.2
The statement in comment #10 is correct. The statement in comment #12 is incorrect. For kernel series 2.6.37+, CONFIG_LOCK_KERNEL can only be turned back on by setting the new option: Kernel hacking ==> Big Kernel Lock to [*]. This will set both CONFIG_BKL=y CONFIG_LOCK_KERNEL=y This is required apparently because the vmmon.ko module still requires the BKL symbols to build. The vmware-modules-1.0.0.25 ebuild should be modified to check for CONFIG_LOCK_KERNEL=y and complain with message pointing to BKL as above.
*** This bug has been confirmed by popular vote. ***
-r4 with BKL check is in portage. Thanks.
Although it's quite commendable that this has been fixed for newer kernels, I really think it is time that Vmware fixed it so that it can work with kernels that has got rid of the BKL completely. I will be running kernels without BKL in the near future.
