Gentoo Archives: gentoo-user

From: "J. Roeleveld" <joost@××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] VirtualBox failed to rebuild
Date: Sat, 07 Jan 2017 16:41:39
Message-Id: E8542743-39C4-4433-807E-5F1E5480DAF2@antarean.org
In Reply to: Re: [gentoo-user] VirtualBox failed to rebuild by gevisz
1 On January 7, 2017 3:30:02 PM GMT+01:00, gevisz <gevisz@×××××.com> wrote:
2 >2017-01-07 15:14 GMT+02:00 Alan McKinnon <alan.mckinnon@×××××.com>:
3 >> On 07/01/2017 14:50, gevisz wrote:
4 >>>>>> Failed to emerge app-emulation/virtualbox-4.3.38, Log file:
5 >>>
6 >>>>>>
7 >'/var/tmp/portage/app-emulation/virtualbox-4.3.38/temp/build.log'
8 >>
9 >> please post the actual error from this file. You will have to do some
10 >> heavy lifting and search for it, it's compiler output
11 >
12 >I have found this warning:
13 >
14 >+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
15 >+++
16 >Hardening is enabled which means that the VBox binaries will not run
17 >from
18 >the binary directory. The binaries have to be installed suid root and
19 >some
20 >more prerequisites have to be fulfilled which is normally done by
21 >installing
22 >the final package. For development, the hardening feature can be
23 >disabled
24 >by specifying the --disable-hardening parameter. Please never disable
25 >that
26 > feature for the final distribution!
27 >+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
28 >+++
29 >
30 >but I never enabled hardening.
31 >
32 >Otherwise, nothing special. Eccept for that that at its end I have the
33 >following:
34 >
35 >Compilation complete. 1 Errors, 0 Warnings, 32 Remarks, 72
36 >Optimizations
37 >x86_64-pc-linux-gnu-gcc -c -O2 -g -pipe -pedantic -Wshadow -Wshadow
38 >-Wall -Wextra -Wno-missing-field-initializers -Wno-unused
39 >-Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter
40 >-Wno-long-long -Wno-long-long -Wmissing-prototypes -Wstrict-prototypes
41 >-Wmissing-declarations -Werror-implicit-function-declaration
42 >-Wno-variadic-macros -march=native -O2 -pipe -fno-omit-frame-pointer
43 >-fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN
44 >-DRT_USE_VISIBILITY_DEFAULT -fPIC -m64
45 >-I/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxAuth/dtrace
46 >-I/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/include
47 >-I/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release
48 >-DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER
49 >-DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__
50 >-DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\"
51 >-DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib64/virtualbox\"
52 >-DRTPATH_SHARED_LIBS=\"/usr/lib64/virtualbox\" -DRTPATH_APP_DOCS=\"\"
53 >-DIN_RING3 -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DVBOX_WITH_DTRACE
54 >-DVBOX_WITH_DTRACE_R3 -DPIC
55 >-Wp,-MD,/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o.dep
56 >-Wp,-MT,/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o
57 >-Wp,-MP -o
58 >/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o
59 >/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/src/VBox/HostServices/auth/pam/VBoxAuthPAM.c
60 >kmk: ***
61 >[/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxDD/vboxssdt-cpuhotplug.hex]
62 >Error 255
63 >kmk: *** Deleting file
64 >`/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxDD/vboxssdt-cpuhotplug.hex'
65 >kmk: *** Waiting for unfinished jobs....
66 >kmk_builtin_append -n
67 >"/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o.dep"
68 >""
69 >"/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/src/VBox/HostServices/auth/pam/VBoxAuthPAM.c:"
70 >""
71 >kmk: *** Exiting with status 2
72 > [31;01m* [0m ERROR: app-emulation/virtualbox-4.3.38::gentoo failed
73 >(compile phase):
74 > [31;01m* [0m emake failed
75 > [31;01m* [0m
76 > [31;01m* [0m If you need support, post the output of `emerge --info
77 >'=app-emulation/virtualbox-4.3.38::gentoo'`,
78 > [31;01m* [0m the complete build log and the output of `emerge -pqv
79 >'=app-emulation/virtualbox-4.3.38::gentoo'`.
80 > [31;01m* [0m The complete build log is located at
81 >'/var/tmp/portage/app-emulation/virtualbox-4.3.38/temp/build.log'.
82 > [31;01m* [0m The ebuild environment file is located at
83 >'/var/tmp/portage/app-emulation/virtualbox-4.3.38/temp/environment'.
84 > [31;01m* [0m Working directory:
85 >'/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38'
86 > [31;01m* [0m S:
87 >'/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38'
88 >!!! When you file a bug report, please include the following
89 >information:
90 >GENTOO_VM= CLASSPATH=""
91 >JAVA_HOME="/etc/java-config-2/current-system-vm"
92 >JAVACFLAGS="" COMPILER=""
93 >and of course, the output of emerge --info =virtualbox-4.3.38
94
95 Please attach the full file. You are not providing the actual error message.
96
97 --
98 Joost
99 --
100 Sent from my Android device with K-9 Mail. Please excuse my brevity.

Replies

Subject Author
Re: [gentoo-user] VirtualBox failed to rebuild gevisz <gevisz@×××××.com>