>> 2.4 Is an out-of-source build approach supported?
> 
> Of course.

Is the output directory called "out" by default?
Can it be achieved that this folder will not be stored within the source
file hierarchy?


> It seems that you're fighting the build system instead of using it.

Another build try brought me a bit further.
Should it also work with the setting 
"VBOX_JAVA_HOME:=/usr/lib64/jvm/java-1.7.0-openjdk-1.7.0"
in the file "LocalConfig.kmk"?


How should I resolve the following error message?

...
kmk: *** 
[/home/elfring/Projekte/VirtualBox/4.3.18/out/linux.amd64/release/obj/RuntimeR0Drv/r0drv/linux/alloc-r0drv-linux.o]
 Error 1
The failing command:
@gcc -c -O2 -nostdinc -iwithprefix include -include 
/lib/modules/3.8.13/build/include/linux/kconfig.h -Wall -Wextra 
-Wno-missing-field-initializers -Wno-unused -Wno-trigraphs 
-fdiagnostics-show-option -Wno-unused-parameter -Wstrict-prototypes 
-Wno-pointer-sign -Wno-sign-compare -fdiagnostics-show-option 
-fno-stack-protector -O2 -mtune=generic -fno-omit-frame-pointer 
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -include 
/home/elfring/Projekte/VirtualBox/4.3.18/include/VBox/SUPDrvMangling.h -m64 
-mno-red-zone -mcmodel=kernel -mno-sse -mno-mmx -mno-sse2 -mno-3dnow 
-fno-reorder-blocks -ffreestanding -fno-asynchronous-unwind-tables 
-funit-at-a-time -Wno-sign-compare -Wdeclaration-after-statement 
-I/home/elfring/Projekte/VirtualBox/4.3.18/src/VBox/Runtime/r0drv/linux 
-I/home/elfring/Projekte/VirtualBox/4.3.18/src/VBox/Runtime 
-I/home/elfring/Projekte/VirtualBox/4.3.18/src/VBox/Runtime/include 
-I/lib/modules/3.8.13/build/include -I/lib/modules/3.8.13/build!
 /include/a
sm-i386/mach-default -I/lib/modules/3.8.13/build/include/asm-x86/mach-default 
-I/lib/modules/3.8.13/build/include/drm 
-I/lib/modules/3.8.13/build/arch/x86/include 
-I/lib/modules/3.8.13/build/arch/x86/include/asm/mach-default 
-I/lib/modules/3.8.13/build/arch/x86/include/uapi 
-I/lib/modules/3.8.13/build/arch/x86/include/generated 
-I/lib/modules/3.8.13/build/arch/x86/include/generated/uapi 
-I/lib/modules/3.8.13/build/include/uapi 
-I/lib/modules/3.8.13/build/include/generated/uapi 
-I/lib/modules/3.8.13/build/include 
-I/home/elfring/Projekte/VirtualBox/4.3.18/out/linux.amd64/release/obj/RuntimeR0Drv/dtrace
 -I/home/elfring/Projekte/VirtualBox/4.3.18/include 
-I/home/elfring/Projekte/VirtualBox/4.3.18/out/linux.amd64/release -DVBOX 
-DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_LINUX 
-D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_HARDENING 
-DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox\" 
-DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" !
 -DRTPATH_S
HARED_LIBS=\"/usr/local/lib/virtualbox\" 
-DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DIN_RING0 -DIN_RT_R0 
-DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -D__KERNEL__ -DMODULE -DIN_RT_R0 
-DRT_WITH_VBOX -DRT_WITHOUT_NOCRT_WRAPPERS -DRT_NO_EXPORT_SYMBOL -DMODULE 
-DKBUILD_MODNAME=KBUILD_STR\(vboxdrv\) -DKBUILD_BASENAME=KBUILD_STR\(vboxdrv\) 
-DIN_SUP_R0 
-Wp,-MD,/home/elfring/Projekte/VirtualBox/4.3.18/out/linux.amd64/release/obj/RuntimeR0Drv/r0drv/linux/alloc-r0drv-linux.o.dep
 
-Wp,-MT,/home/elfring/Projekte/VirtualBox/4.3.18/out/linux.amd64/release/obj/RuntimeR0Drv/r0drv/linux/alloc-r0drv-linux.o
 -Wp,-MP -o 
/home/elfring/Projekte/VirtualBox/4.3.18/out/linux.amd64/release/obj/RuntimeR0Drv/r0drv/linux/alloc-r0drv-linux.o
 
/home/elfring/Projekte/VirtualBox/4.3.18/src/VBox/Runtime/r0drv/linux/alloc-r0drv-linux.c
In file included from /lib/modules/3.8.13/build/include/linux/cred.h:17:0,
                 from /lib/modules/3.8.13/build/include/linux/sched.h:56,
                 from 
/home/elfring/Projekte/VirtualBox/4.3.18/src/VBox/Runtime/r0drv/linux/the-linux-kernel.h:92,
                 from 
/home/elfring/Projekte/VirtualBox/4.3.18/src/VBox/Runtime/r0drv/linux/assert-r0drv-linux.c:31:
/lib/modules/3.8.13/build/include/linux/key.h: At top level:
/lib/modules/3.8.13/build/include/linux/key.h:210:22: error: field 'keys' has 
incomplete type
   struct assoc_array keys;
                      ^
...

Regards,
Markus

_______________________________________________
vbox-dev mailing list
[email protected]
https://www.virtualbox.org/mailman/listinfo/vbox-dev

Reply via email to