From owner-freebsd-emulation@FreeBSD.ORG Mon Sep 14 16:42:05 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A5FB1065672 for ; Mon, 14 Sep 2009 16:42:05 +0000 (UTC) (envelope-from fli@shapeshifter.se) Received: from mx1.h3q.net (mx1.h3q.net [IPv6:2001:16d8:ffe5:1::f1]) by mx1.freebsd.org (Postfix) with ESMTP id BD3D38FC14 for ; Mon, 14 Sep 2009 16:42:04 +0000 (UTC) Received: from smtp-auth.h3q.net (smtp-auth.h3q.net [127.0.0.1]) (Authenticated sender: hidden) by mx1.h3q.net (Postfix) with ESMTPSA id 34F6233DF8 ; Mon, 14 Sep 2009 18:42:02 +0200 (CEST) Message-ID: <4AAE7259.80200@shapeshifter.se> Date: Mon, 14 Sep 2009 18:42:01 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 2.0.0.23 (X11/20090912) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> In-Reply-To: <20090914153800.38fb8e7a@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?Zahemszky_G=E1bor?= , freebsd-emulation@freebsd.org Subject: Re: virtualbox cannot compile X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2009 16:42:05 -0000 Gary Jennejohn wrote: > On Mon, 14 Sep 2009 14:29:16 +0200 > Zahemszky G__bor wrote: > >> Mon, 14 Sep 2009 13:26:02 +0200 -n >> Gary Jennejohn __rta: >> >>> On Mon, 14 Sep 2009 09:48:05 +0200 >>> Zahemszky G__bor (by way of Zahemszky G__bor >>> ) wrote: >>> >>>> I've got a problem with the (last two) recent version(s) of the >>>> emulators/virtualbox port, as I cannot compile it. It fails with a: >>>> >>>> 02/src/VBox/Runtime/r0drv/freebsd/alloc-r0drv-freebsd.c:34: >>>> /sys/vm/vm.h:64:24: error: machine/vm.h: No such file or directory >>>> >>>> error message. The previous version failed with the same problem. >>>> >>> Have you generated a kernel lately? I believe machine is a symbolic >>> link which is created when you make a kernel, but I might be wrong. >>> >>> Om my box I >>> have: /usr/obj/usr/src/sys/amd64/machine >>> -> /usr/src/sys/amd64/include >> Hm. Interesting: I've generated kernels in the not too past. But. I use >> i386, and not amd64, and GENERIC kernel on it. I >> have /usr/obj/usr/src/sys/ and in it, GENERIC and boot directory. And I >> have GENERIC/machine/vm.h in it. So I think, some configuration steps >> have some problems. >> > > I just compiled the latest svn stuff and it also fails (copy&paste => long lines): > > kBuild: Compiling vboxnetflt - /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c > In file included from /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c:43: > /sys/sys/socket.h:39:28: error: machine/_align.h: No such file or directory > kmk[2]: *** [/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o] Error 1 > The failing command: > @cc -c -O2 -Wall -Wextra -Wno-missing-field-initializers -Wno-unused > -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes > -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 > -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common > -finline-limit=8000 -fno-stack-protector -O2 -mtune=generic > -fno-omit-frame-pointer -nostdinc -std=c99 -m64 --param inline-unit-growth=100 > --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel > -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -Wundef > -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt > -I/sys -I/sys/contrib/altq -I/sys/../include -I/usr/include > -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/include > -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release > -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING > -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox\" > -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" > -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" > -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DRT_OS_FREEBSD > -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -D_KERNEL -DKLD_MODULE -DIN_RING0 > -DIN_RT_R0 -DIN_RT_R0 > -Wp,-MD,/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o.dep > -Wp,-MT,/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o > -Wp,-MP > -o /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c > > Definitely looks like there's a bug in the new networking stuff. It compiles fine for me on FreeBSD 7.2-amd64 using the latest version in ports, builds both vboxnetflt.ko and vboxnetadp.ko. Have you tried the one in ports (although I can't imagine why the svn-version wouldn't work)? What version of FreeBSD are you using ? Fredrik