Mike Jakubik wrote:
On 01/13/14 03:42, Bernhard Fröhlich wrote:
On Mon, Jan 13, 2014 at 7:46 AM, Craig Rodrigues rodr...@freebsd.org
wrote:
There is really no reason to make that dance so complicated or why you
need to destroy your /usr/ports.
WARNING: If there are issues with that ports
On 01/13/14 03:42, Bernhard Fröhlich wrote:
On Mon, Jan 13, 2014 at 7:46 AM, Craig Rodrigues rodr...@freebsd.org wrote:
There is really no reason to make that dance so complicated or why you
need to destroy your /usr/ports.
WARNING: If there are issues with that ports please contact jkim@
On 01/17/14 14:17, Mike Jakubik wrote:
Just wanted to let everyone know this compiles and works perfect for
me on 10.0-PRE. The only issue I have is with the vboxwebsrv rc.d
script, when I try to start it nothing happens, no errors, however
manually running vboxwebsrv -b does the job. Thanks
On Mon, Jan 13, 2014 at 7:46 AM, Craig Rodrigues rodr...@freebsd.org wrote:
On Sun, Jan 12, 2014 at 5:36 PM, Miguel Clara miguelmcl...@gmail.comwrote:
I tried this approach and still get errors:
kmk: ***
On Sun, Jan 12, 2014 at 5:36 PM, Miguel Clara miguelmcl...@gmail.comwrote:
I tried this approach and still get errors:
kmk: ***
[/tmp/tmp/xy/jkim/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/VBoxSVC/src-server/ApplianceImpl.o]
I tried
Am 11.01.2014 03:49 schrieb Craig Rodrigues rodr...@freebsd.org:
Hi,
I had problems with the virtualbox-ose-4.22 port
under FreeBSD 10.0-RC5, where VirtualBox would occasionally
crash.
It looks like the mix of QT C++ libraries compiled with clang,
vs. the virtualbox-ose port compiled with
On Sat, Jan 11, 2014 at 1:09 PM, Bernhard Fröhlich de...@bluelife.atwrote:
Am 11.01.2014 03:49 schrieb Craig Rodrigues rodr...@freebsd.org:
(5) Build and install gsoap from jkim's port (you need to do this
because the version of gsoap in the ports tree will result in failed
compilation):
On Sat, Jan 11, 2014 at 1:09 PM, Bernhard Fröhlich de...@bluelife.atwrote:
I still think this is the wrong approach and I won't maintain all those
clang patches in the official port. The problem that I see is that we are
diverging from upstream vbox too much and end up maintaining a very
Hi,
I had problems with the virtualbox-ose-4.22 port
under FreeBSD 10.0-RC5, where VirtualBox would occasionally
crash.
It looks like the mix of QT C++ libraries compiled with clang,
vs. the virtualbox-ose port compiled with g++46 was not a good mix
After reading this post:
