> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Howdy, > > Changelog from VirtualBox is available here: > http://www.virtualbox.org/wiki/Changelog > > Changes in the port: > - VirtualBox and the guest additions have been updated to 3.1.2. > - Port has been renamed to virtualbox-ose to reflect that we are > using the OSE version. Requested by: mm_at_ > - A seperate port for the kernel modules has been created: virtualbox-ose-kmod > - A seperate port for guest additions for FreeBSD guests has been > created: virtualbox-ose-additions > - Added proper PulseAudio support for FreeBSD. Contributed by Noriyoshi Kawano > - procfs is no longer required because vbox uses sysctl(3) now. Contributed by > Baptiste Daroussin and Bernhard Froehlich > - Fix build with a non-standard location for the system source. Submitted > by: scf_at_ > > How to upgrade: > - Fetch the new ports: > # fetch https://svn.bluelife.at/nightlies/virtualbox-port-r601.tar.gz > # tar xf virtualbox-port-r601.tar.gz > > - Build the new ports: > # cd virtualbox-ose-kmod && make > # cd ../virtualbox-ose && make > > - If build was ok, deinstall old port > # pkg_deinstall virtualbox-\* > > - Install new port: > # cd ../virtualbox-ose-kmod && make install clean > # cd ../virtualbox-ose && make install clean > > For FreeBSD guests within VirtualBox please try the new guest additions port: > # fetch https://svn.bluelife.at/nightlies/virtualbox-port-r601.tar.gz > # tar xf virtualbox-port-r601.tar.gz > # cd virtualbox-ose-additions && make install clean > # /usr/local/etc/rc.d/vboxguest.sh start > > Check that the VirtualBox kernel module is loaded via loader.conf > and reboot the machine. > > Check the wiki page for known problems: http://wiki.freebsd.org/VirtualBox > > Please report any functionality which was working with previous versions of > VirtualBox and no longer working with 3.1.2 or any build failure. > > Many thanks to the VirtualBox developers, all tester and patch submitter > and the whole vbox_at_ team. > > > Happy Testing! when compiling it under X11 (ie from an xterm), the configuration fails when checking for Mesa: ... Checking for Mesa / GLU: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 137 (DRI2) Minor opcode of failed request: 1 (DRI2Connect) Serial number of failed request: 19 Current serial number in output stream: 19 ===> Script "configure" failed unexpectedly. ... the check is wrong since it's checking the compile 'environment'. my workaround is: ( unsetenv DISPLAY ; make ) cheers dannyReceived on Mon Dec 28 2009 - 14:09:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:59 UTC