Date: Wed, 18 Feb 2015 16:42:22 +0100 (CET) From: Tommy Scheunemann <net@arrishq.net> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: vbox@freebsd.org Subject: Re: Compiling fails at 10.1-RELEASE Message-ID: <alpine.BSF.2.11.1502181640040.1066@tscheunemann_bsd> In-Reply-To: <54E382E1.10805@FreeBSD.org> References: <alpine.BSF.2.11.1502171507430.1027@tscheunemann_bsd> <54E3807B.7090205@FreeBSD.org> <54E382E1.10805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Feb 2015, Jung-uk Kim wrote: > On 02/17/2015 12:55, Jung-uk Kim wrote: >> On 02/17/2015 09:16, Tommy Scheunemann wrote: >>> Hello there, >> >>> after updating the ports tree a bit ago, VirtualBox came along >>> with an update from the installed 4.3.20_4 to 4.3.22. Each >>> installed port (gcc-4.8.4, kBuild etc.) is up to date, still the >>> compile run fails with the following error: >>> >>> ---- SNIP ---- kBuild: Compiling VBoxRemPrimary - >>> ... >>> kmk: *** Exiting with status 2 **e *** Error code 1 >> >>> Stop. make: stopped in /usr/src/ports/emulators/virtualbox-ose >> >>> ===>>> make build failed for emulators/virtutart from the point >>> of failure with this command line: portmaster <flags> >>> emulators/virtualbox-ose >>>---- SNIP ---- >>> >>> My "make.conf" looks like: >>> >>> ---- SNIP ---- >>> ... >>> ---- SNIP ---- >> >>> And the port is configured with: >> >>> DBUS, GUESTADDITIONS, QT4, UDPTUNNEL, X11 >> >>> enabled. The rest of the settings is disabled. >> >>> Running a "make distclean" and another "make" doesn't help and >>> the error is reproducible. What has been changed is that the >>> PORTSDIR is mounted under /usr/src/ports, though the environment >>> variable has been set - in case that causes problems. Also >>> removing the CFLAGS options (or better the FORTIFY_SOURCE) >>> doesn't help much. So, is there anything else I can do at my end >>> ? Maybe changing options of the port ? Basically DBUS isn't maybe >>> required, UDPTUNNEL might be - X11 and QT4 yes because the >>> intention is to run a Windows - if possible with the seamless >>> option. >> >> It looks like you're using ccache. I believe you need to disable >> it. Please try "make NOCCACHE=yes". > > Please see the following ccache PR: > > https://bugzilla.samba.org/show_bug.cgi?id=7827 > > Especially, Comment 4 and 5. > > Jung-uk Kim Hello, Yup - disabling ccache was it. Kind regards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1502181640040.1066>