app-emulation/vmware-modules-1.0.0.23-r1 and 2.6.30-gentoo Reproducible: Didn't try Steps to Reproduce: 1.emerge -av vmware-modules Actual Results: >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.23-r1 * vmware-modules-1.0.0.23-r1.amd64.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.30-gentoo >>> Unpacking source... >>> Unpacking vmware-modules-1.0.0.23-r1.amd64.tar.bz2 to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmmon.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmnet.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmblock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmblock-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmci.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmci-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vsock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vsock-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] * Applying 1.0.0.23-r1-kernel-2.6.29.patch ... [ ok ] * Applying 1.0.0.23-makefile-kernel-dir.patch ... [ ok ] >>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work >>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work ... * Preparing vmmon module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux Using 2.6.x kernel build system. make -C /usr/src/linux M=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/linux/driver.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/linux/driverLog.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/linux/hostif.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/comport.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/cpuid.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/hashFunc.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/memtrack.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/phystrack.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/task.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.o In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:54: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/./include/x86svm.h:50:1: warning: "MSR_VM_CR" redefined In file included from /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/msr.h:4, from /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/processor.h:21, from /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/thread_info.h:22, from include/linux/thread_info.h:55, from include/linux/preempt.h:9, from include/linux/spinlock.h:50, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:56, from include/linux/sched.h:54, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:32: /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/msr-index.h:374:1: warning: this is the location of the previous definition In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:54: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/./include/x86svm.h:53:1: warning: "MSR_VM_HSAVE_PA" redefined In file included from /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/msr.h:4, from /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/processor.h:21, from /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/thread_info.h:22, from include/linux/thread_info.h:55, from include/linux/preempt.h:9, from include/linux/spinlock.h:50, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:56, from include/linux/sched.h:54, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:32: /usr/src/linux-2.6.30-gentoo/arch/x86/include/asm/msr-index.h:375:1: warning: this is the location of the previous definition CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmcore/moduleloop.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmmon.o Building modules, stage 2. MODPOST 1 modules CC /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmmon.mod.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. make[1]: `postbuild' is up to date. make[1]: Leaving directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only' cp -f vmmon.ko ./../vmmon.o * Preparing vmnet module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux Using 2.6.x kernel build system. make -C /usr/src/linux M=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/driver.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/hub.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/userif.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/netif.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/bridge.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/filter.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/procfs.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/smac_compat.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/smac.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vnetEvent.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vnetUserListener.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vmnet.mod.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. make[1]: `postbuild' is up to date. make[1]: Leaving directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only' cp -f vmnet.ko ./../vmnet.o * Preparing vmblock module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux Using 2.6.x kernel build system. make -C /usr/src/linux M=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/block.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.o /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.c: In function 'SetupProcDevice': /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.c:159: error: 'struct proc_dir_entry' has no member named 'owner' /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.c:171: error: 'struct proc_dir_entry' has no member named 'owner' make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.o] Error 1 make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only] Error 2 make[1]: *** [sub-make] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo' make: *** [vmblock.ko] Error 2 * * ERROR: app-emulation/vmware-modules-1.0.0.23-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3713: Called linux-mod_src_compile * environment, line 2827: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/environment'. * >>> Failed to emerge app-emulation/vmware-modules-1.0.0.23-r1, Log file: >>> '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/build.log' * Messages for package app-emulation/vmware-modules-1.0.0.23-r1: * * ERROR: app-emulation/vmware-modules-1.0.0.23-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3713: Called linux-mod_src_compile * environment, line 2827: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/environment'. * Expected Results: _
See bug #270150 for a workaround.
I've commited new vmware-modules ebuild to portage tree. It has patches for 2.6.29 and 2.6.30.
(In reply to comment #2) > I've commited new vmware-modules ebuild to portage tree. It has patches for > 2.6.29 and 2.6.30. > Trying to emerge vmware-modules-1.0.0.24 on gentoo-sources-2.6.30-r2 has the same issue, again.
Created attachment 200905 [details] Output from `uname -a`
Created attachment 200908 [details] Output from `emerge --info`
Created attachment 200910 [details] Output from `FEATURES="-distcc" emerge -v =app-emulation/vmware-modules-1.0.0.23-r1`
<a href="http://bugs.gentoo.org/attachment.cgi?id=200905">Output from `uname -a`</a> <a href="http://bugs.gentoo.org/attachment.cgi?id=200908">Output from `emerge --info`</a> <a href="http://bugs.gentoo.org/attachment.cgi?id=200910">Output from `FEATURES="-distcc" emerge -v =app-emulation/vmware-modules-1.0.0.23-r2`</a> <b>Additional Info:</b> This is a brand new system build. I cannot emerge ANY version of vmware-modules. I've tried all in my portage tree... vmware-modules-1.0.0.15-r1.ebuild vmware-modules-1.0.0.15-r2.ebuild vmware-modules-1.0.0.23-r1.ebuild vmware-modules-1.0.0.23.ebuild vmware-modules-1.0.0.24.ebuild ...and several in a local portage overlay. I've tried all of them with every conceivable configuration of USE, FEATURES, keywords and et cetera. No dice. In any case, with respect to 1.0.0.23-r1 on a 2.6.30 kernel, as is specifically cited in this bug, the bug still exists.
Created attachment 200911 [details] Output from `FEATURES="-distcc" emerge -v =app-emulation/vmware-modules-1.0.0.23-r2`
Comment on attachment 200910 [details] Output from `FEATURES="-distcc" emerge -v =app-emulation/vmware-modules-1.0.0.23-r1` Spartan vmware-modules # FEATURES="-distcc" emerge -v =app-emulation/vmware-modules-1.0.0.23-r1 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-emulation/vmware-modules-1.0.0.23-r1 0 kB Total: 1 package (1 new), Size of downloads: 0 kB >>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.23-r1 * vmware-modules-1.0.0.23-r1.amd64.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.30-gentoo-r4/build * Found sources for kernel version: * 2.6.30-gentoo-r4 >>> Unpacking source... >>> Unpacking vmware-modules-1.0.0.23-r1.amd64.tar.bz2 to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmmon.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmnet.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmblock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmblock-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vmci.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vmci-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Unpacking ./vmware-modules-1.0.0.23-r1/vsock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work * Converting vsock-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] * Applying 1.0.0.23-r1-kernel-2.6.29.patch ... [ ok ] * Applying 1.0.0.23-makefile-kernel-dir.patch ... [ ok ] >>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work >>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work ... * Preparing vmmon module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build Using 2.6.x kernel build system. make -C /lib/modules/2.6.30-gentoo-r4/build M=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo-r4' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/linux/driver.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/linux/driverLog.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/linux/hostif.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/comport.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/cpuid.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/hashFunc.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/memtrack.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/phystrack.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/task.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.o In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:54: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/./include/x86svm.h:50:1: warning: "MSR_VM_CR" redefined In file included from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/msr.h:4, from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/processor.h:21, from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/thread_info.h:22, from include/linux/thread_info.h:55, from include/linux/preempt.h:9, from include/linux/spinlock.h:50, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:56, from include/linux/sched.h:54, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:32: /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/msr-index.h:374:1: warning: this is the location of the previous definition In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:54: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/./include/x86svm.h:53:1: warning: "MSR_VM_HSAVE_PA" redefined In file included from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/msr.h:4, from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/processor.h:21, from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/thread_info.h:22, from include/linux/thread_info.h:55, from include/linux/preempt.h:9, from include/linux/spinlock.h:50, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:56, from include/linux/sched.h:54, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/common/vmx86.c:32: /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/msr-index.h:375:1: warning: this is the location of the previous definition CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmcore/moduleloop.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmmon.o Building modules, stage 2. MODPOST 1 modules CC /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmmon.mod.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. make[1]: `postbuild' is up to date. make[1]: Leaving directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmmon-only' cp -f vmmon.ko ./../vmmon.o * Preparing vmnet module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build Using 2.6.x kernel build system. make -C /lib/modules/2.6.30-gentoo-r4/build M=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo-r4' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/driver.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/hub.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/userif.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/netif.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/bridge.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/filter.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/procfs.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/smac_compat.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/smac.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vnetEvent.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vnetUserListener.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vmnet.mod.o LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. make[1]: `postbuild' is up to date. make[1]: Leaving directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmnet-only' cp -f vmnet.ko ./../vmnet.o * Preparing vmblock module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build Using 2.6.x kernel build system. make -C /lib/modules/2.6.30-gentoo-r4/build M=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo-r4' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/block.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.o /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.c: In function 'SetupProcDevice': /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.c:159: error: 'struct proc_dir_entry' has no member named 'owner' /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.c:171: error: 'struct proc_dir_entry' has no member named 'owner' make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only/linux/control.o] Error 1 make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/work/vmblock-only] Error 2 make[1]: *** [sub-make] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4' make: *** [vmblock.ko] Error 2 * * ERROR: app-emulation/vmware-modules-1.0.0.23-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3730: Called linux-mod_src_compile * environment, line 2844: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/app-emulation:vmware-modules-1.0.0.23-r1:20090811-043719.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/environment'. * >>> Failed to emerge app-emulation/vmware-modules-1.0.0.23-r1, Log file: >>> '/var/log/portage/app-emulation:vmware-modules-1.0.0.23-r1:20090811-043719.log' * Messages for package app-emulation/vmware-modules-1.0.0.23-r1: * * ERROR: app-emulation/vmware-modules-1.0.0.23-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3730: Called linux-mod_src_compile * environment, line 2844: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/app-emulation:vmware-modules-1.0.0.23-r1:20090811-043719.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23-r1/temp/environment'. *
for 2.6.30 kernel you need 1.0.0.24 vmware modules it has "owner" patch or 2.6.30 patch You said you tried 1.0.0.24, please attach build log.
(In reply to comment #10) > for 2.6.30 kernel you need 1.0.0.24 vmware modules > it has "owner" patch or 2.6.30 patch > You said you tried 1.0.0.24, please attach build log. > 1.0.0.24 is one of the version I had listed above that would not build. Over night I did a full sync and emerged world. vmware-modules-1.0.0.24 build now; however... Spartan ~ # emerge -p vmware-workstation These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD] app-emulation/vmware-modules-1.0.0.23-r1 [1.0.0.24] [ebuild N ] x11-libs/libview-0.6.2 USE="debug" [ebuild N ] dev-cpp/libsexymm-0.1.9 USE="debug -doc" [ebuild N ] dev-python/cython-0.11.2 USE="-doc -examples" [ebuild N ] dev-python/lxml-2.2.1 USE="threads -doc -examples" [ebuild IN F ] app-emulation/vmware-workstation-6.5.2.156735 ...the ebuild for vmware-workstation does not want modules 1.0.0.24.
(In reply to comment #10) > for 2.6.30 kernel you need 1.0.0.24 vmware modules > it has "owner" patch or 2.6.30 patch > You said you tried 1.0.0.24, please attach build log. > The RDEPEND parameters for vmware-workstation-6.5.2.156735.ebuild: ~app-emulation/vmware-modules-1.0.0.23 !<app-emulation/vmware-modules-1.0.0.23 !>=app-emulation/vmware-modules-1.0.0.24
In vmware-workstation-6.5.2.156735.ebuild, the original RDEPEND variable has: ~app-emulation/vmware-modules-1.0.0.23 !<app-emulation/vmware-modules-1.0.0.23 !>=app-emulation/vmware-modules-1.0.0.24 I moved the entire portage entry (/usr/local/portage/app-emulation/vmware-workstation) to my local portage overlay and changed the RDEPEND segment to be... ~app-emulation/vmware-modules-1.0.0.24 !<app-emulation/vmware-modules-1.0.0.23 !>app-emulation/vmware-modules-1.0.0.24 ...and was able to start emerge vmware-workstation 6.5.2.156735 with vmware-modules 1.0.0.24. The process bailed out on the first attempt, forcing me to first rebuild python with sqlite and ncurses support (which went smoothly). Then I try to emerge vmware-workstation (which defaults to version 6.5.2.156735). It appears to be trying, but the EULA displays with no option to accept it. There is nothing along the lines of "Do you accept [y/n]?" in or around the EULA. I'm wondering, however, if this might be some sort of display problem because, if I CTRL+C to cancel the ebuild, I cannot see what I'm typing (but typing a command and hitting ENTER does execute the command). At this point I have to issue 'reset' command to normalize my console. Any ideas on this? In any case, the RDEPEND entries related to vmware-modules in vmware-workstation-6.5.2.156735.ebuild preclude vmware-modules-1.0.0.24 and attempts to use a lesser version of vmware-modules. Fixing this as noted above in a local portage overlay gets me past all previously-stated issues. I think I'm on the road to success - I'll know for sure if I can get past the EULA. :)
(In reply to comment #13) > I moved the entire portage entry > (/usr/local/portage/app-emulation/vmware-workstation) to my local portage Or you could just unmask app-emulation/vmware-workstation-6.5.2.156735-r1
(In reply to comment #13) >It appears to be trying, but the EULA displays with no option >to accept it. There is nothing along the lines of "Do you accept [y/n]?" in or >around the EULA. Are you sure that you scrolled to the end of EULA and not looking at first page?
(In reply to comment #14) > (In reply to comment #13) > > > I moved the entire portage entry > > (/usr/local/portage/app-emulation/vmware-workstation) to my local portage > > Or you could just unmask app-emulation/vmware-workstation-6.5.2.156735-r1 > Absolutely. I just wanted an isolated version to manipulate without touching the original.
