Re: gcc-4.5 and 4.6 needs to be recompiled due to /usr/src/UPDATE: 20110608:

On 06/09/11 17:18, Attilio Rao wrote:
> 2011/6/9 Mark Linimon <linimon_at_lonesome.com>:
>> Things that change the way the base system behaves w/rt ports need
>> version bumps.
> 
> BTW, could someone provide an actual error message?
> 
> I assume these errors are caused by cpumask_t going away.

For emulators/virtualbox-ose-kmod ..

cc -O2 -pipe -march=prescott -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0
-DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING
-DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -fno-strict-aliasing -Werror
-D_KERNEL -DKLD_MODULE -nostdinc  -Iinclude -I. -Ir0drv -I. -I_at_
-I_at_/contrib/altq -finline-limit=8000 --param inline-unit-growth=100
--param large-function-growth=1000 -fno-common   -mno-align-long-strings
-mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float
-ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector
-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option -c
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c

/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:
In function 'RTMpOnOthers':
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167:
error: 'cpumask_t' undeclared (first use in this function)

/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167:
error: (Each undeclared identifier is reported only once
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167:
error: for each function it appears in.)

Without a version bump, it becomes impossible to determine if a
version-specific patch can be applied to accommodate the ABI change,

	imb