Bug 345145 – app-emulation/vmware-modules-1.0.0.2[4-6] doesn't compile with kernel >=2.6.37

• Status: RESOLVED TEST-REQUEST
• Product: Gentoo Linux

[Description Fabio Rossi 2010-11-11 20:53:43 UTC]

Here is the error:

/var/tmp/portage/app-emulation/vmware-modules-1.0.0.24-r1/work/vmci-only/linux/driver.c: In function ‘LinuxDriver_Open’:
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.24-r1/work/vmci-only/linux/driver.c:363: error: implicit declaration of function ‘init_MUTEX’
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.24-r1/work/vmci-only/linux/driver.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.24-r1/work/vmci-only] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/usr/src/wireless-testing'
make: *** [vmci.ko] Error 2
 * ERROR: app-emulation/vmware-modules-1.0.0.24-r1 failed:
 *   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
 * 
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 4129:  Called linux-mod_src_compile
 *   environment, line 3067:  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}";
 * 
 * If you need support, post the output of 'emerge --info =app-emulation/vmware-modules-1.0.0.24-r1',
 * the complete build log and the output of 'emerge -pqv =app-emulation/vmware-modules-1.0.0.24-r1'.
 * This ebuild is from an overlay: '/var/lib/layman/__mine__/'
 * The complete build log is located at '/var/log/portage/app-emulation:vmware-modules-1.0.0.24-r1:20101111-205114.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.24-r1/temp/environment'.
 * S: '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.24-r1/work'

[Comment 1 Fabio Rossi 2010-11-11 22:14:43 UTC]

Created attachment 254043 [details, diff]
1.0.0.24-semainit.patch

Here is the proposed patch

[Comment 2 Fabio Rossi 2010-11-11 22:15:50 UTC]

Created attachment 254045 [details, diff]
1.0.0.26-semainit.patch

Here is the patch for vmware-modules-1.0.0.26

[Comment 3 andcycle-gentoo 2011-01-14 21:41:06 UTC]

(In reply to comment #1)
> Created an attachment (id=254043) [details]
> 1.0.0.24-semainit.patch
> 
> Here is the proposed patch
> 

just tried the patch, works well on my system,
I am using vmware-server 2.0.2 and it depends on 1.0.0.24

by the way, bug #351592 has passed 1.0.0.25 as been resolved

[Comment 4 andcycle-gentoo 2011-01-14 21:43:12 UTC]

(In reply to comment #3)
> (In reply to comment #1)
> > Created an attachment (id=254043) [details] [details]
> > 1.0.0.24-semainit.patch
> > 
> > Here is the proposed patch
> > 
> 
> just tried the patch, works well on my system,
> I am using vmware-server 2.0.2 and it depends on 1.0.0.24
> 
> by the way, bug #351592 has passed 1.0.0.25 as been resolved
> 
sorry foy cp the wrong bug number, I mean #349649

[Comment 5 Vadim Kuznetsov (RETIRED) 2011-01-15 17:33:55 UTC]

fixed in cvs. thanks.

[Comment 6 Fabio Rossi 2011-01-20 20:55:35 UTC]

The vmware-modules-1.0.0.24-r3.ebuild is wrong considering future kernel versions. I'm using 2.6.38-rc1 and doesn't work anymore...

Please change
  kernel_is 2 6 37 && epatch "${FILESDIR}/${PV}-sema.patch" 
to
  kernel_is ge 2 6 37 && epatch "${FILESDIR}/${PV}-sema.patch"