Date: Fri, 3 May 2013 00:13:58 +0200 From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@FreeBSD.org> To: Mark Johnston <markjdb@gmail.com> Cc: Viren Shah <virenshah@gmail.com>, Glen Barber <gjb@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: Virtualbox addition in FreeBSD -current guest OS? Message-ID: <CAE-m3X3RWkvZxmnHwFobLD0apNmKG=SAX9q-uvWB=3wDj%2BjOHw@mail.gmail.com> In-Reply-To: <20130426174352.GA33054@gloom.sandvine.com> References: <CAJa23VM-YNhifaWULzeT_meh0bPjE8aqeRgMfZaG0mfmHjfFeQ@mail.gmail.com> <20130426144955.GF1617@glenbarber.us> <20130426150210.GA29463@gloom.sandvine.com> <20130426150735.GG1617@glenbarber.us> <20130426174352.GA33054@gloom.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This should be fixed together with the update to 4.2.12 now. On Fri, Apr 26, 2013 at 7:43 PM, Mark Johnston <markjdb@gmail.com> wrote: > On Fri, Apr 26, 2013 at 11:07:35AM -0400, Glen Barber wrote: >> On Fri, Apr 26, 2013 at 11:02:10AM -0400, Mark Johnston wrote: >> > On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen Barber wrote: >> > > On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote: >> > > > I was having problems compiling the virtualbox guest additions on a FBSD >> > > > -current (Apr 23 20:30 EDT) system. I changed all the VM_OBJECT_LOCKs to >> > > > VM_OBJECT_WLOCKs (and same for the UNLOCKS) and added rwlock.h to the >> > > > includes. That enabled it to compile but I'm having problems getting X >> > > > started (it just hangs) using those vbox modules for xorg. Log msg (see >> > > > attached) says "failed to initialize VirtualBox device (rc=-102)" >> > > > >> > > > Anyone having recently compiled the vbox ose-additions on a -current system >> > > > and had it work? I'm just trying to figure out if this is a >> > > > -current-related issue or a vbox related one. >> > > > >> > > >> > > This was fixed months ago, I think. Is your ports tree updated? >> > >> > As far as the compilation issue goes, the virtualbox-ose-kmod port is >> > indeed fixed but virtualbox-ose-additions is still broken on current >> > with the latest ports tree. >> >> *sigh*... Is this broken "again" or broken "still" ? > > Looks like the latter based on the port's revision history. It was just > never fixed when the lock changed to a rwlock. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X3RWkvZxmnHwFobLD0apNmKG=SAX9q-uvWB=3wDj%2BjOHw>