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

On Fri, Jun 10, 2011 at 8:22 AM, Garrett Cooper <yanegomi_at_gmail.com> wrote:
> On Thu, Jun 9, 2011 at 3:26 PM, Attilio Rao <attilio_at_freebsd.org> wrote:
>> 2011/6/9 Michael Butler <imb_at_protected-networks.net>:
>>> 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,
>>
>> Well, the ports should be working against -CURRENT, so what you say is
>> not entirely true.
>> Second thing, yeah, it is cpumask_t going away, so someone needs  to
>> sit there, check what usage of cpumask_t was done and replace with
>> proper code.
>> It seems usual port maintenance due by the maintainer IMHO.
>>
>> I'm not entirely sure how bumping __FreeBSD_version may help right now.
>
>    This also impacts recompiling the base system if you don't nuke
> /usr/obj (output from make buildworld buildkernel, no -j).
> Thanks,
> -Garrett
>
> c++ -O2 -pipe -fno-strict-aliasing -pipe
> -I/usr/obj/usr/src/sys/FALLOUT
> -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-strict-aliasing -pipe
> -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib
> -I/usr/src/gnu/usr.bin/gperf -c
> /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/list-node.cc
> c++ -O2 -pipe -fno-strict-aliasing -pipe
> -I/usr/obj/usr/src/sys/FALLOUT
> -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-strict-aliasing -pipe
> -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib
> -I/usr/src/gnu/usr.bin/gperf -c
> /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc
> In file included from
> /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc:25:
> /usr/include/sys/types.h:102: error: '__cpumask_t' does not name a type
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/gperf.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.

    I just realized that my environment may be at fault for this item
(I was trying to debug something -- note the first -I argument).
Please ignore and move on unless more reports come in.
Thanks,
-Garrett