Vmware Modules test, merge log

vmware-modules-279.1-test_merge.log (text/x-log), 19.23 KB, created by John on 2014-01-20 01:06:45 UTC

Ebuild test, install, merge logs.

/Portage/app-emulation/vmware-modules # ebuild vmware-modules-279.1.ebuild test
Forcing test.
>>> Existing ${T}/environment for 'vmware-modules-279.1' will be sourced.
>>> Run 'clean' to start with a fresh environment.
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'pretend' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.pretended' to force pretend.
>>> It appears that 'setup' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.setuped' to force setup.
>>> It appears that 'unpack' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.unpacked' to force unpack.
>>> It appears that 'prepare' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.prepared' to force prepare.
>>> It appears that 'configure' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.configured' to force configure.
>>> Compiling source in /Build/portage/app-emulation/vmware-modules-279.1/work ...
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmblock module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.mod.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.ko
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmci module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
cp -f vmci.ko ./../vmci.o
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmmon module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driverLog.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1252:4: error: too many arguments to function ‘smp_call_function’
    compat_smp_call_function(LinuxDriverSyncCallHook, &args, 0);
    ^
In file included from /Source/linux-3.12.7-gentoo/include/linux/percpu.h:5:0,
                 from /Source/linux-3.12.7-gentoo/include/linux/percpu-rwsem.h:6,
                 from /Source/linux-3.12.7-gentoo/include/linux/fs.h:30,
                 from /Source/linux-3.12.7-gentoo/include/linux/highmem.h:4,
                 from /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:25:
/Source/linux-3.12.7-gentoo/include/linux/smp.h:94:5: note: declared here
 int smp_call_function(smp_call_func_t func, void *info, int wait);
     ^
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: At top level:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
/Source/linux-3.12.7-gentoo/scripts/Makefile.build:308: recipe for target '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o' failed
make[3]: *** [/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o] Error 1
/Source/linux-3.12.7-gentoo/Makefile:1228: recipe for target '_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only' failed
make[2]: *** [_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
Makefile:130: recipe for target 'vmmon.ko' failed
make: *** [vmmon.ko] Error 2
 * ERROR: app-emulation/vmware-modules-279.1 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1'`.
 * The complete build log is located at '/Files/Portage-Logs/app-emulation:vmware-modules-279.1:20140119-223333.log'.
 * For convenience, a symlink to the build log is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only'
 * S: '/Build/portage/app-emulation/vmware-modules-279.1/work'


Install:

tripled vmware-modules # ebuild vmware-modules-279.1.ebuild install
>>> Existing ${T}/environment for 'vmware-modules-279.1' will be sourced.
>>> Run 'clean' to start with a fresh environment.
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'pretend' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.pretended' to force pretend.
>>> It appears that 'setup' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.setuped' to force setup.
>>> It appears that 'unpack' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.unpacked' to force unpack.
>>> It appears that 'prepare' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.prepared' to force prepare.
>>> It appears that 'configure' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.configured' to force configure.
>>> Compiling source in /Build/portage/app-emulation/vmware-modules-279.1/work ...
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmblock module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.mod.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.ko
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmci module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
cp -f vmci.ko ./../vmci.o
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmmon module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driverLog.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1252:4: error: too many arguments to function ‘smp_call_function’
    compat_smp_call_function(LinuxDriverSyncCallHook, &args, 0);
    ^
In file included from /Source/linux-3.12.7-gentoo/include/linux/percpu.h:5:0,
                 from /Source/linux-3.12.7-gentoo/include/linux/percpu-rwsem.h:6,
                 from /Source/linux-3.12.7-gentoo/include/linux/fs.h:30,
                 from /Source/linux-3.12.7-gentoo/include/linux/highmem.h:4,
                 from /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:25:
/Source/linux-3.12.7-gentoo/include/linux/smp.h:94:5: note: declared here
 int smp_call_function(smp_call_func_t func, void *info, int wait);
     ^
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: At top level:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
/Source/linux-3.12.7-gentoo/scripts/Makefile.build:308: recipe for target '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o' failed
make[3]: *** [/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o] Error 1
/Source/linux-3.12.7-gentoo/Makefile:1228: recipe for target '_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only' failed
make[2]: *** [_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
Makefile:130: recipe for target 'vmmon.ko' failed
make: *** [vmmon.ko] Error 2
 * ERROR: app-emulation/vmware-modules-279.1 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1'`.
 * The complete build log is located at '/Files/Portage-Logs/app-emulation:vmware-modules-279.1:20140119-223333.log'.
 * For convenience, a symlink to the build log is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only'
 * S: '/Build/portage/app-emulation/vmware-modules-279.1/work'

Merge:

tripled vmware-modules # ebuild vmware-modules-279.1.ebuild merge
>>> Existing ${T}/environment for 'vmware-modules-279.1' will be sourced.
>>> Run 'clean' to start with a fresh environment.
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'pretend' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.pretended' to force pretend.
>>> It appears that 'setup' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.setuped' to force setup.
>>> It appears that 'unpack' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.unpacked' to force unpack.
>>> It appears that 'prepare' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.prepared' to force prepare.
>>> It appears that 'configure' has already executed for 'vmware-modules-279.1'; skipping.
>>> Remove '/Build/portage/app-emulation/vmware-modules-279.1/.configured' to force configure.
>>> Compiling source in /Build/portage/app-emulation/vmware-modules-279.1/work ...
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmblock module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.mod.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.ko
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmci module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
cp -f vmci.ko ./../vmci.o
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vmmon module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build 
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driverLog.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1252:4: error: too many arguments to function ‘smp_call_function’
    compat_smp_call_function(LinuxDriverSyncCallHook, &args, 0);
    ^
In file included from /Source/linux-3.12.7-gentoo/include/linux/percpu.h:5:0,
                 from /Source/linux-3.12.7-gentoo/include/linux/percpu-rwsem.h:6,
                 from /Source/linux-3.12.7-gentoo/include/linux/fs.h:30,
                 from /Source/linux-3.12.7-gentoo/include/linux/highmem.h:4,
                 from /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:25:
/Source/linux-3.12.7-gentoo/include/linux/smp.h:94:5: note: declared here
 int smp_call_function(smp_call_func_t func, void *info, int wait);
     ^
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: At top level:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
/Source/linux-3.12.7-gentoo/scripts/Makefile.build:308: recipe for target '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o' failed
make[3]: *** [/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o] Error 1
/Source/linux-3.12.7-gentoo/Makefile:1228: recipe for target '_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only' failed
make[2]: *** [_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
Makefile:130: recipe for target 'vmmon.ko' failed
make: *** [vmmon.ko] Error 2
 * ERROR: app-emulation/vmware-modules-279.1 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1'`.
 * The complete build log is located at '/Files/Portage-Logs/app-emulation:vmware-modules-279.1:20140119-223333.log'.
 * For convenience, a symlink to the build log is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only'
 * S: '/Build/portage/app-emulation/vmware-modules-279.1/work'