Created attachment 406110 [details] emerge -pqv '=app-emulation/vmware-modules-279.3-r1::vmware' I'm trying to upgrade the whole system but now vmware-modules cannot be compiled anymore. Here's some output: ben ~# uname -a Linux ben 4.0.5-gentoo #3 SMP Fri Jul 2 18:47:46 CEST 2015 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux ben ~# emerge vmware-modules Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/vmware-modules-279.3-r1::vmware * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/4.0.5-gentoo/build * Found sources for kernel version: * 4.0.5-gentoo * Checking for suitable kernel configuration options... [ ok ] * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work >>> Preparing source in /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work ... * Applying 279-makefile-kernel-dir.patch ... [ ok ] * Applying 279-makefile-include.patch ... [ ok ] * Applying 279-netdevice.patch ... [ ok ] * Applying 279-apic.patch ... [ ok ] * Applying 279-putname.patch ... [ ok ] * Applying 279-vmblock.patch ... [ ok ] * Applying 279-3.10-00-userns.patch ... [ ok ] * Applying 279-3.10-01-getname.patch ... [ ok ] * Applying 279-3.10-03-deprecated.patch ... [ ok ] * Applying 279-3.10-04-dentry.patch ... [ ok ] * Applying 279-3.10-05-inode.patch ... [ ok ] * Applying 279-filldir.patch ... [ ok ] * Applying 279-3.15-00-readlink.patch ... [ ok ] * Applying 279-3.15-01-vsock.patch ... [ ok ] * Applying 279-3.17-00-netdev.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work ... * Preparing vmblock module make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/4.0.5-gentoo/build Using 2.6.x kernel build system. make -C /lib/modules/4.0.5-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory '/usr/src/linux-4.0.5-gentoo' make[2]: Entering directory '/usr/src/linux-4.0.5-gentoo' CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/filesystem.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/stubs.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/file.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/block.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/inode.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/super.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/control.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/module.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/dentry.o /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/filesystem.c: In function ‘Iget’: /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/filesystem.c:325:21: error: storage size of ‘actualNd’ isn’t known struct nameidata actualNd; ^ /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/filesystem.c:325:21: warning: unused variable ‘actualNd’ [-Wunused-variable] /usr/src/linux-4.0.5-gentoo/scripts/Makefile.build:258: recipe for target '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/filesystem.o' failed make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/filesystem.o] Error 1 make[3]: *** Waiting for unfinished jobs.... /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/file.c: In function ‘FileOpOpen’: /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/file.c:95:18: error: ‘struct file’ has no member named ‘f_dentry’ if (actualFile->f_dentry && inode == actualFile->f_dentry->d_inode) { ^ /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/file.c:95:51: error: ‘struct file’ has no member named ‘f_dentry’ if (actualFile->f_dentry && inode == actualFile->f_dentry->d_inode) { ^ /usr/src/linux-4.0.5-gentoo/scripts/Makefile.build:258: recipe for target '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/file.o' failed make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/file.o] Error 1 /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’: /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/dentry.c:66:21: error: storage size of ‘actualNd’ isn’t known struct nameidata actualNd; ^ /var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/dentry.c:66:21: warning: unused variable ‘actualNd’ [-Wunused-variable] /usr/src/linux-4.0.5-gentoo/scripts/Makefile.build:258: recipe for target '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/dentry.o' failed make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only/linux/dentry.o] Error 1 /usr/src/linux-4.0.5-gentoo/Makefile:1390: recipe for target '_module_/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only' failed make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only] Error 2 make[2]: Leaving directory '/usr/src/linux-4.0.5-gentoo' Makefile:145: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.0.5-gentoo' Makefile:130: recipe for target 'vmblock.ko' failed make: *** [vmblock.ko] Error 2 * ERROR: app-emulation/vmware-modules-279.3-r1::vmware failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.3-r1::vmware'`, * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.3-r1::vmware'`. * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only' * S: '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work' >>> Failed to emerge app-emulation/vmware-modules-279.3-r1, Log file: >>> '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/temp/build.log' * Messages for package app-emulation/vmware-modules-279.3-r1: * ERROR: app-emulation/vmware-modules-279.3-r1::vmware failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.3-r1::vmware'`, * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.3-r1::vmware'`. * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work/vmblock-only' * S: '/var/tmp/portage/app-emulation/vmware-modules-279.3-r1/work' I have tried to compile it even with 'USE="vmci vsock" emerge vmware-modules" or 'USE="-vmci -vsock" emerge vmware-modules' but without success. It's a blocking problem because I cannot even open Workstation or Player anymore. I don't think the problem might be related with the latest kernel (4.0.5 from current portage) but maybe something else, I have had troubles like that in the past. Please see attachments to understand the current situation. What should I try to re-emerge vmware-modules again ? is there someone with the same setup and issues ? Thanks in advance for your reply Ben
Created attachment 406112 [details] emerge --info '=app-emulation/vmware-modules-279.3-r1::vmware'
I have also tried to use several portage overlays (vmware, archenroot, open-relay) to understand if other ebuilds would solve this problem but I didn't had any good result at all.
Fixed temporarily with a little hack. See my latest comment on (https://bugs.gentoo.org/show_bug.cgi?id=462666#c46). I have enabled VMCI and VSOCKETS on the kernel, created a local portage with Alex Dubenetsky attachment (https://bugs.gentoo.org/show_bug.cgi?id=462666#c45) and emerged vmware-modules with : 'USE="-vmci -vsock" emerge vmware-modules'. A dirty hack but it works, I personally don't like it that much and I prefer to keep my machines as clean as possible without local portages or layman's overlays. I'd like to keep official gentoo repos only and applicate your suggested solutions. I'd like to roll back to the official package whenever it's possible, please let me know if you need to experiment or want to do some tests on my machine ~# uname -a Linux ben 4.0.5-gentoo #8 SMP Mon Jul 6 00:11:51 CEST 2015 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux
The latest official vmware overlay has had the version bumped. I have built the sources for vmware-modules-{271,279,304} on stock kernels 3.10 - 4.0, and associated vmware-workstation-{9,10,11} ebuilds. Please give those a try and let me know if you have any issues. Thanks
*** This bug has been marked as a duplicate of bug 539972 ***
