Date: Sun, 28 Oct 2012 15:40:00 +0100 From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox and non-default compiler Message-ID: <CAE-m3X1U_KGX7iYLEwqzhifHQMQJaaYf-S4Kk5jfdKgtQ08f=Q@mail.gmail.com> In-Reply-To: <503E1AA6.4010304@FreeBSD.org> References: <503E1AA6.4010304@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 29, 2012 at 3:35 PM, Andriy Gapon <avg@freebsd.org> wrote: > > There is another issue with building virtualbox-ose port using a non-defa= ult > compiler. CFLAGS/CXXFLAGS and LDFLAGS defined by ports framework (and us= er) are > not passed to virtualbox build at all. > So, whatever bsd.gcc.mk carefully configures for e.g. gcc46 is not reflec= ted in > the build. Most importantly this is -Wl,-rpath option in LDFLAGS that sh= ould > ensure that the correct C++ run-time libraries are picked up. > > I do not know how pass those make variables to kBuild-based virtualbox bu= ild. CFLAGS/CXXFLAGS/LDFLAGS are a bit handcrafted and generated in: https://www.virtualbox.org/browser/vbox/trunk/Config.kmk#L3254 That stuff is used for kernel module and userland code. --=20 Bernhard Fr=F6hlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X1U_KGX7iYLEwqzhifHQMQJaaYf-S4Kk5jfdKgtQ08f=Q>