Date: Thu, 15 Mar 2012 20:28:27 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: freebsd-questions@freebsd.org Cc: Mike Clarke <jmc-freebsd2@milibyte.co.uk> Subject: Re: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2 Message-ID: <44haxp75jo.fsf@lowell-desk.lan> In-Reply-To: <44y5r177mm.fsf@lowell-desk.lan> (Lowell Gilbert's message of "Thu, 15 Mar 2012 19:43:29 -0400") References: <201203131413.41392.jmc-freebsd2@milibyte.co.uk> <44y5r177mm.fsf@lowell-desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> writes: > Mike Clarke <jmc-freebsd2@milibyte.co.uk> writes: > >> portmaster -a fails with: >> >> cc -O -pipe -march=athlon-mp -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 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/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-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -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 -c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c >> /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: >> In function 'rtR0MemObjFreeBSDAllocPhysPages': >> /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: >> error: invalid type argument of '->' >> *** Error code 1 >> >> Stop >> in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. >> >> I ran portsnap immediately before portmaster so my ports are up to date. >> >> Any suggestions? > > There have been more updates to the port since, and I don't see any > failures in the automated builds. I've got a build on my fast system > (RELENG_8, amd64) running now for a check, but it will take a while to > grab the distfiles. You might want to grab the latest port and try it. And it builds fine for me. My best advice is: clean out the directory for that port, update again, and see if the problem is the same.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44haxp75jo.fsf>