Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 252059 Details for
Bug 342285
app-emulation/vmware-modules-1.0.0.26: failes to build on 2.6.36 kernel
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
/var/log/portage/app-emulation:vmware-modules-1.0.0.26:20101026-172935.log
app-emulation:vmware-modules-1.0.0.26:20101026-172935.log (text/plain), 9.08 KB, created by
Toralf Förster
on 2010-10-26 17:30:19 UTC
(
hide
)
Description:
/var/log/portage/app-emulation:vmware-modules-1.0.0.26:20101026-172935.log
Filename:
MIME Type:
Creator:
Toralf Förster
Created:
2010-10-26 17:30:19 UTC
Size:
9.08 KB
patch
obsolete
> [32;01m*[0m CPV: app-emulation/vmware-modules-1.0.0.26 > [32;01m*[0m REPO: gentoo > [32;01m*[0m USE: elibc_glibc kernel_linux userland_GNU x86 > [32;01m*[0m Determining the location of the kernel source code > [32;01m*[0m Found kernel source directory: > [32;01m*[0m /usr/src/linux > [32;01m*[0m Found kernel object directory: > [32;01m*[0m /lib/modules/2.6.36/build > [32;01m*[0m Found sources for kernel version: > [32;01m*[0m 2.6.36 >>>> Unpacking source... >>>> Unpacking vmware-modules-1.0.0.26.x86.tar.bz2 to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Unpacking ./vmware-modules-1.0.0.26/vmblock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Unpacking ./vmware-modules-1.0.0.26/vmci.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Unpacking ./vmware-modules-1.0.0.26/vmmon.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Unpacking ./vmware-modules-1.0.0.26/vmnet.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Unpacking ./vmware-modules-1.0.0.26/vsock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work >>>> Preparing source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work ... > [32;01m*[0m Applying 1.0.0.26-makefile-kernel-dir.patch ... >[A[112C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying 1.0.0.26-makefile-include.patch ... >[A[112C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying apic.patch ... >[A[112C [34;01m[ [32;01mok[34;01m ][0m >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work ... > [32;01m*[0m Preparing vmblock module >make -j2 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.36/build >Using 2.6.x kernel build system. >make -C /lib/modules/2.6.36/build SUBDIRS=$PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= modules >make[1]: Entering directory `/usr/src/linux-2.6.36' >make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/block.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/control.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/dbllnklst.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/dentry.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/file.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/filesystem.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/inode.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/module.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/stubs.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/linux/super.o > LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/vmblock.o > Building modules, stage 2. > MODPOST 1 modules > CC /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/vmblock.mod.o > LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/vmblock.ko >make[1]: Leaving directory `/usr/src/linux-2.6.36' >make -C $PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= postbuild >make[1]: Entering directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-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.26/work/vmblock-only' >cp -f vmblock.ko ./../vmblock.o > [32;01m*[0m Preparing vmci module >make -j2 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.36/build >Using 2.6.x kernel build system. >make -C /lib/modules/2.6.36/build SUBDIRS=$PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= modules >make[1]: Entering directory `/usr/src/linux-2.6.36' >make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/linux/driver.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/linux/driverLog.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/linux/vmciKernelIf.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciContext.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciDatagram.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciDriver.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciDs.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciEvent.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciGroup.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciHashtable.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciProcess.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciQueuePair.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/common/vmciResource.o > LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/vmci.o > Building modules, stage 2. > MODPOST 1 modules > CC /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/vmci.mod.o > LD [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/vmci.ko >make[1]: Leaving directory `/usr/src/linux-2.6.36' >make -C $PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= postbuild >make[1]: Entering directory `/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-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.26/work/vmci-only' >cp -f vmci.ko ./../vmci.o > [32;01m*[0m Preparing vmmon module >make -j2 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.36/build >Using 2.6.x kernel build system. >make -C /lib/modules/2.6.36/build SUBDIRS=$PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= modules >make[1]: Entering directory `/usr/src/linux-2.6.36' >make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/driver.o >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/driver.c: In function âinit_moduleâ: >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/driver.c:422: error: âstruct file_operationsâ has no member named âioctlâ >make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/driver.o] Error 1 >make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only] Error 2 >make[1]: *** [sub-make] Error 2 >make[1]: Leaving directory `/usr/src/linux-2.6.36' >make: *** [vmmon.ko] Error 2 > [31;01m*[0m ERROR: app-emulation/vmware-modules-1.0.0.26 failed: > [31;01m*[0m Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.36/build > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 54: Called src_compile > [31;01m*[0m environment, line 3860: Called linux-mod_src_compile > [31;01m*[0m environment, line 2931: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m 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}"; > [31;01m*[0m > [31;01m*[0m If you need support, post the output of 'emerge --info =app-emulation/vmware-modules-1.0.0.26', > [31;01m*[0m the complete build log and the output of 'emerge -pqv =app-emulation/vmware-modules-1.0.0.26'. > [31;01m*[0m The complete build log is located at '/var/log/portage/app-emulation:vmware-modules-1.0.0.26:20101026-172935.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/temp/environment'. > [31;01m*[0m S: '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 342285
: 252059 |
252061