Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 232581 Details for
Bug 321179
app-emulation/vmware-modules-1.0.0.26 fails to build on recent xen kernels 2.6.31||2.6.32
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log when building vmware-modules with kernel xen-sources-2.6.32-r1
build_2632.log (text/plain), 10.03 KB, created by
Evgeniy Zaitsev
on 2010-05-23 13:51:04 UTC
(
hide
)
Description:
build.log when building vmware-modules with kernel xen-sources-2.6.32-r1
Filename:
MIME Type:
Creator:
Evgeniy Zaitsev
Created:
2010-05-23 13:51:04 UTC
Size:
10.03 KB
patch
obsolete
> [32;01m*[0m CPV: app-emulation/vmware-modules-1.0.0.26 > [32;01m*[0m REPO: gentoo > [32;01m*[0m USE: amd64 elibc_glibc kernel_linux multilib userland_GNU > [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 sources for kernel version: > [32;01m*[0m 2.6.32-xen-r1-xen-roger17 >>>> Unpacking source... >>>> Unpacking vmware-modules-1.0.0.26.amd64.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[103C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying 1.0.0.26-makefile-include.patch ... >[A[103C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying apic.patch ... >[A[103C [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 -j9 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 SUBDIRS=$PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= modules >make[1]: Entering directory `/usr/src/linux-2.6.32-xen-r1' >make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. > Updating /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmblock-only/Makefile.xen > 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.32-xen-r1' >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 -j9 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 SUBDIRS=$PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= modules >make[1]: Entering directory `/usr/src/linux-2.6.32-xen-r1' >make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. > Updating /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmci-only/Makefile.xen > 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.32-xen-r1' >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 -j9 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 SUBDIRS=$PWD SRCROOT=$PWD/. \ > MODULEBUILDDIR= modules >make[1]: Entering directory `/usr/src/linux-2.6.32-xen-r1' >make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. > Updating /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/Makefile.xen > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/driver.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/driverLog.o > CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.o >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.c: In function âHostIF_APICInitâ: >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.c:2692: error: âFIX_APIC_BASEâ undeclared (first use in this function) >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.c:2692: error: (Each undeclared identifier is reported only once >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.c:2692: error: for each function it appears in.) >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.c: In function âHostIF_APIC_IDâ: >/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.c:2737: error: âFIX_APIC_BASEâ undeclared (first use in this function) >make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.26/work/vmmon-only/linux/hostif.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.32-xen-r1' >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=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 > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 54: Called src_compile > [31;01m*[0m environment, line 3872: Called linux-mod_src_compile > [31;01m*[0m environment, line 2969: 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/tmp/portage/app-emulation/vmware-modules-1.0.0.26/temp/build.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 321179
:
232577
|
232579
| 232581 |
232583