Re: [gentoo-user] vmware-server error log

[William Kenworthy]

You still need to post messages from further back - this is still the
results, not the cause.  Also, does 1.0.0.15 support later kernels? - I
am using 1.0.0.25 and workstation 6.5 with 2.6.28 - and even there had
to use the layman vmware overlay.  vmware usually lags behind current
kernels, and you usually have to jump through a few hoops to even keep
close to up to date.

BillK



On Sat, 2009-09-05 at 12:11 +0000, Nick Khamis wrote:
> Hey Everyone,
>
> I have been at this for a week now, going from amd64 to x86. I still
> want to use 2.6.30-r5. When trying to build vmware-server this is the
> error I am presented with:
>
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c: In function 'LinuxDriver_Open':
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:579: error: 'struct task_struct' has no member named 'euid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c: In function '__LinuxDriver_Ioctl':
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1530: error: 'struct task_struct' has no member named 'suid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1531: error: 'struct task_struct' has no member named 'cap_permitted'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1796: error: 'struct task_struct' has no member named 'euid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1796: error: 'struct task_struct' has no member named 'uid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1797: error: 'struct task_struct' has no member named 'fsuid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1797: error: 'struct task_struct' has no member named 'uid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1798: error: 'struct task_struct' has no member named 'egid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1798: error: 'struct task_struct' has no member named 'gid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1799: error: 'struct task_struct' has no member named 'fsgid'
> /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.c:1799: error: 'struct task_struct' has no member named 'gid'
> make[3]: ***
> [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only/linux/driver.o] Error 1
> make[2]: ***
> [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/work/vmmon-only] Error 2
> make[1]: *** [sub-make] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r5'
> make: *** [vmmon.ko] Error 2
>  *
>  * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
>  * Call stack:
>  *               ebuild.sh, line   49:  Called src_compile
>  *             environment, line 3723:  Called
> linux-mod_src_compile
>  *             environment, line 2841:  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=i686-pc-linux-gnu-gcc
> CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   auto-build
> VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux
> KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build
>  *
>  * 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.15-r2/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'.
>  *
>
>
> Your Help Is Greatly Apprecited,
>
> Reagrds,
> Ninus
>
-- 
William Kenworthy <billk@×××××××××.au>
Home in Perth!