This Question is Answered
1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
5 Replies
Last post:
Jul 15, 2008 9:04 AM by
ric_k
lagriffe wrote:
christaylor wrote:
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
That's your explanation there. In order to build modules that will load into your kernel, you need to have kernel header files that match your running kernel. I don't know what distro you're using, but you should be able to download kernel headers that match your kernel. Then try the process again.There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
no, that's not the explanation. the error message says "There is probably a slight difference...". the last few days I spent my time building several kernel configurations for my debian sid/unstable box. first i tried the 2.6.25 debian packaged kernel sources and then 2.6.26 vanilla. everytime i needed to use the any-any-patches, but still it did not compile the vmmon-module. it failed at the exact same position as posted by christaylor - even though i just tried to install vmware player 2.0.4 but i believe it's the same reason.
by chance i found the vmware community posts by a user called selinux that stated that "init_mm" is not present anymore in new kernels. the only solution to that (for now) as i can see is to Enable unused/obsolete exported symbols in Kernel Hackings for your kernel configuration - and recompile the kernel.
after that vmmon compiles just fine. vmblock still does not compile, but vmware-configuration completes successfully, since vmblock is not vital.
now i can gladly report, that vmware player 2.0.4 is running just fine on my debian box with 2.6.26 vanilla kernel.
