Date: Mon, 14 Sep 2009 14:35:06 -0300 (BRT) From: "Mario Lobo" <mlobo@digiart.art.br> To: gary.jennejohn@freenet.de Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox cannot compile Message-ID: <29199.200.249.56.17.1252949706.squirrel@squirrel.sv4.hmnoc.net> In-Reply-To: <20090914190136.773147aa@ernst.jennejohn.org> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> <4AAE7259.80200@shapeshifter.se> <20090914190136.773147aa@ernst.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, 14 Sep 2009 18:42:01 +0200 > Fredrik Lindberg <fli@shapeshifter.se> wrote: > > [big snip] > Gary Jennejohn wrote: >> > 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 ? >> > > 9-current amd64. > > I didn't try the port. > > Hmm. My sources are newer than the kernel I'm using. Don't know whether > that is a factor or not. > > --- That was definetly a factor for me. I had a backup I made of /usr/src just before csuping a new source tree, which issued the same error you are getting. As soon as I restored to the old /usr/src, Vbox compiled without errors. The error I kept getting was machine/vm.h: No such file or directory On my new /usr/src, /usr/src/sys/vm/vm.h has a # include <machine/vm.h> directive which the old source does not. Mario Lobo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29199.200.249.56.17.1252949706.squirrel>