From owner-freebsd-questions@FreeBSD.ORG Fri Mar 16 00:28:36 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C427106564A for ; Fri, 16 Mar 2012 00:28:36 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from asbnvacz-mailrelay01.megapath.net (asbnvacz-mailrelay01.megapath.net [207.145.128.243]) by mx1.freebsd.org (Postfix) with ESMTP id BF8E68FC12 for ; Fri, 16 Mar 2012 00:28:35 +0000 (UTC) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.52]) by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id C473CA7167F for ; Thu, 15 Mar 2012 20:28:34 -0400 (EDT) Received: (qmail 17107 invoked from network); 16 Mar 2012 00:28:34 -0000 Received: by simscan 1.4.0 ppid: 28059, pid: 10670, t: 0.1924s scanners: clamav: 0.88.2/m:52/d:13513 Received: from unknown (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Mar 2012 00:28:34 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.8]) by be-well.ilk.org (Postfix) with ESMTP id 363EB33C1E; Thu, 15 Mar 2012 20:28:28 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 9EAC039860; Thu, 15 Mar 2012 20:28:27 -0400 (EDT) From: Lowell Gilbert To: freebsd-questions@freebsd.org References: <201203131413.41392.jmc-freebsd2@milibyte.co.uk> <44y5r177mm.fsf@lowell-desk.lan> Date: Thu, 15 Mar 2012 20:28:27 -0400 In-Reply-To: <44y5r177mm.fsf@lowell-desk.lan> (Lowell Gilbert's message of "Thu, 15 Mar 2012 19:43:29 -0400") Message-ID: <44haxp75jo.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Mike Clarke Subject: Re: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 00:28:36 -0000 Lowell Gilbert writes: > Mike Clarke 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.