Date: Sat, 8 Aug 2009 22:18:50 +0200 From: Beat Gaetzi <beat@FreeBSD.org> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox not building on -current Message-ID: <26f6c7210908081318p7b29d299yb27c826fba1438ff@mail.gmail.com> In-Reply-To: <4A7DD9E4.3000900@FreeBSD.org> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> <4A7DD9E4.3000900@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/8/8 Doug Barton <dougb@freebsd.org>: > Beat Gaetzi wrote: > >> The current svn port fixes a lot of known problems (also for HEAD) so >> I hope we could update the port before the port freeze. > > Can you post a patch to the existing port so that I can give it a try? Please try this patch: http://people.freebsd.org/~beat/vbox/virtualbox-cvs-3.0.51r22072.patch >> - Some users reported problems updating virtualbox with portmaster >> (same problem with devel/kBuild). Unfortunately I hadn't time to >> verify this yet. > > Yes, this is a known issue, and the problem is in kBuild. Portmaster > uses a number of environment variables to do its work and they seem to > be overflowing kBuild's stack. I see. Thanks for the information. Beat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26f6c7210908081318p7b29d299yb27c826fba1438ff>