Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 332400 Details for
Bug 447302
app-emulation/virtualbox-modules-4.2.4 with gentoo-sources-3.7.0 - Header files were moved and re-organized, causes a build failure.
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Build Log for virtualbox-modules-4.1.22 (also broken by new kernel)
build.log (text/plain), 8.53 KB, created by
James
on 2012-12-15 20:31:52 UTC
(
hide
)
Description:
Build Log for virtualbox-modules-4.1.22 (also broken by new kernel)
Filename:
MIME Type:
Creator:
James
Created:
2012-12-15 20:31:52 UTC
Size:
8.53 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: app-emulation/virtualbox-modules-4.1.22 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: polynomial-c@gentoo.org patrick@gentoo.org,swapon@gmail.com >[32;01m * [39;49;00mUSE: amd64 consolekit elibc_glibc kernel_linux multilib policykit userland_GNU >[32;01m * [39;49;00mFEATURES: ccache sandbox >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory > [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/3.7.0-gentoo/build > [32;01m*[0m Found sources for kernel version: > [32;01m*[0m 3.7.0-gentoo >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >>>> Unpacking source... >>>> Unpacking vbox-kernel-module-src-4.1.22.tar.xz to /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work >>>> Source unpacked in /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >>>> Preparing source in /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work ... >>>> Source prepared. >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >>>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work ... >>>> Source configured. >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >>>> Compiling source in /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work ... >ln: failed to create symbolic link âModule.symversâ: File exists > [32;01m*[0m Preparing vboxdrv module >make -j7 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' KERN_DIR=/usr/src/linux KERNOUT=/lib/modules/3.7.0-gentoo/build all >*** Building 'vboxdrv' module *** >make[1]: Entering directory `/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv' >make KBUILD_VERBOSE= SUBDIRS=/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv SRCROOT=/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv CONFIG_MODULE_SIG= -C /usr/src/linux modules >make[2]: Entering directory `/usr/src/linux-3.7.0-gentoo' > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/linux/SUPDrv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/SUPDrv.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/SUPDrvSem.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/alloc-r0drv.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/initterm-r0drv.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/memobj-r0drv.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/mpnotification-r0drv.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/powernotification-r0drv.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/assert-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/alloc-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/initterm-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/memobj-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/mp-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/semevent-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/process-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/semeventmulti-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/semfastmutex-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/semmutex-r0drv-linux.o > CC [M] /var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/spinlock-r0drv-linux.o >/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ârtR0MemObjNativeMapUserâ: >/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: error: âVM_RESERVEDâ undeclared (first use in this function) >/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: note: each undeclared identifier is reported only once for each function it appears in >make[3]: *** [/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Error 1 >make[3]: *** Waiting for unfinished jobs.... >make[2]: *** [_module_/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv] Error 2 >make[2]: Leaving directory `/usr/src/linux-3.7.0-gentoo' >make[1]: *** [vboxdrv] Error 2 >make[1]: Leaving directory `/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work/vboxdrv' >make: *** [all] Error 2 > [31;01m*[0m ERROR: app-emulation/virtualbox-modules-4.1.22 failed (compile phase): > [31;01m*[0m emake failed > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-4.1.22'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-4.1.22'`. > [31;01m*[0m The complete build log is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work' > [31;01m*[0m S: '/var/tmp/portage/app-emulation/virtualbox-modules-4.1.22/work' >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory >chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
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 447302
:
332336
| 332400 |
333178