virtualbox-ose 4.0.8 fails

Matt sendtomatt at
Fri Jun 24 17:14:41 UTC 2011

On 06/24/11 09:41, George Kontostanos wrote:
> Hi everyone,
> I am trying to compile virtualbox-ose 4.0.8 but it fails with
> /out/freebsd.amd64/debug -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE
> -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\"
> -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\"
> -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\"
> -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\"
> -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o.dep
> -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o
> -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp
> kmk: *** Waiting for unfinished jobs....
> kmk: *** Exiting with status 2
> *** Error code 2
> Stop in /usr/ports/emulators/virtualbox-ose.
> *** Error code 1
> Stop in /usr/ports/emulators/virtualbox-ose.
> I have even try to build with debug symbols but I don't see anything
> different. The system is running GENERIC kernel with debug options
> disabled.
> options         COMPAT_FREEBSD32
> Is included in the kernel as I saw that this has caused similar
> problems in the past.
> Any help would be appreciated
It fails a couple ways actually, first on an isDVD in a disk system 
request...commenting out the inq_(something, not in front of machine 
with recent svn) parts of that code yields virtualbox compiling, but 
failing during kmod compile due to the recent change (without revision 
bump) from cpumask_t to cpuset_t.

It seems like recent CAM changes and CPU change are going to require 
some changes to virtualbox in HostHardwareFreeBSD.c and mp-r0drv.c at 
least. Even though OS revision was not bumped, perhaps Makefile can 
switch on presence of cpuset userland utility?

Luckily I only csup'd a machine I don't really need Vbox on, so I'm 
holding back all other machines until Vbox maintainers sort out the issue.


More information about the freebsd-current mailing list