I have a KBUILD_OUTPUT_PREFIX set to /var/tmp/kernel-output and have built my 2.6.8-gentoo-r7 kernel to output there. After emerging app-emulation/vmware-workstation-4.5.2.8848-r1, I attempt to run /opt/vmware/bin/vmware-config.pl, and encounter the following "brick wall": What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] The path "/usr/src/linux/include" is an existing directory, but it does not contain at least one of these directories "linux", "asm", "net" as expected. I presume the ebuild doesn't yet know about the config-kernel koutput options? Please advise. ptd Reproducible: Always Steps to Reproduce: 1. config-kernel --set-symlink=2.6.8-gentoo-r7 2. config-kernel --make-koutput=current 3. cp <good config file> /var/tmp/kernel-output/.config 4. cd /usr/src/linux 5. make oldconfig 6. emerge && emerge modules_install 7. emerge vmware-workstation 8. /opt/vmware/bin/vmware-config.pl Actual Results: vmware-config.pl fails to find the files it needs, to wit: What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] The path "/usr/src/linux/include" is an existing directory, but it does not contain at least one of these directories "linux", "asm", "net" as expected. Expected Results: Should have found the files under /var/tmp/kernel-config and proceeded to build its modules successfully.
I can only confirm this, vmware can currently only be used by setting 'config-kernel --allow-writable=yes' which is considered a security risk!
From http://ftp.cvut.cz/vmware/readme.txt: vmware-any-any-update --- update51 --- Added support for building modules for 2.6.x kernels built with KBUILD_OUTPUT=... defined in the environment. Due to vmware-config.pl you cannot build modules in these configurations with simple 'vmware-config.pl', but direct 'make' in untarred vmmon & vmnet packages should work. Building vmmon works fine. But building vmnet gives: /tmp/vmnet-only/bridge.c: In Funktion
From http://ftp.cvut.cz/vmware/readme.txt: vmware-any-any-update --- update51 --- Added support for building modules for 2.6.x kernels built with KBUILD_OUTPUT=... defined in the environment. Due to vmware-config.pl you cannot build modules in these configurations with simple 'vmware-config.pl', but direct 'make' in untarred vmmon & vmnet packages should work. Building vmmon works fine. But building vmnet gives: /tmp/vmnet-only/bridge.c: In Funktion »VNetBridgeReceiveFromVNet«: /tmp/vmnet-only/bridge.c:464: error: structure has no member named `wmem_alloc' Cause: In Makefile.kernel socket.c can't be compiled due to missing include. Workaround: Use `GLOBAL_DEFS="-Iinclude2/asm/mach-default" make` to compile vmnet.o Don't forget to copy vmnet.o and vmmon.o to /lib/modules/`uname -r`/misc
Try version 4.5.2.8848-r2 and see if this fixes your problem.
Is this actually fixed? Using vmware-workstation-5.0.0.13124 still doesn't seem to solve it, and neither did the stable version before.
It should have been NEEDINFO, not FIXED.
Alright, since this is an error with VMWare-supplied code and not the ebuild, I am going to recommend that you contact them for support on this commercial product. I don't feel that I should be spending my time providing support for a commercial vendor's code. I'm more than willing to add any necessary patches to the ebuild to resolve this issue, but don't feel I should be providing VMWare with my services without compensation, as they have their own technical staff.
