Date: Wed, 18 Apr 2012 15:28:04 +1000 From: Petro Rossini <petro.rossini@gmail.com> To: Mario Lobo <lobo@bsd.com.br> Cc: freebsd-emulation@freebsd.org Subject: Re: VBox upgrade fails Message-ID: <CAExkqpdCZNaRY%2Bn%2BQdm%2BbNpTwsDC1KjUo08d0%2BQ6tM-x2v%2B8jQ@mail.gmail.com> In-Reply-To: <201204172314.00889.lobo@bsd.com.br> References: <alpine.BSF.2.00.1204172001310.30965@mail.neu.net> <CAExkqpeOFVb-NuUk_xYfYwHfRceR3DA_Y-xxvOyJqB3Jo5XP1w@mail.gmail.com> <201204172314.00889.lobo@bsd.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 18, 2012 at 12:14 PM, Mario Lobo <lobo@bsd.com.br> wrote: > On Tuesday 17 April 2012 21:13:12 Petro Rossini wrote: >> On Wed, Apr 18, 2012 at 10:03 AM, AN <andy@neu.net> wrote: >> > Trying to update VBox fails with: >> > >> > # portsnap fetch update >> > # pkg_version -vl\< >> > virtualbox-ose-4.1.8 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0< =A0 needs updati= ng (port has 4.1.12) >> >> .. >> >> > *** Building 'vboxdrv' module *** >> > "/usr/share/mk/bsd.own.mk", line 483: MK_CLANG_IS_CC can't be set by a >> > user. *** [all] Error code 1 >> > >> > Stop in >> > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.12/out/fr= eeb >> > sd.amd64/release/bin/src. *** [do-build] Error code 1 >> >> That looks very similar to the compile error I had before on a >> FreeBSD-8 system. I upgraded to FreeBSD-9 and did not see the error >> anymore. >> >> I suspect compiling on FreebSD-8 is broken. > > Totally untrue ! > > [/usr/ports/emulators/virtualbox-ose-kmod]>pkg_info | grep virtualbox > > virtualbox-ose-4.1.12 A general-purpose full virtualizer for x86 hardware > virtualbox-ose-kmod-4.1.12 VirtualBox kernel module for FreeBSD > > # Papi/root [23:09:38] > [/usr/ports/emulators/virtualbox-ose-kmod]>uname -a > > FreeBSD Papi 8.2-STABLE FreeBSD 8.2-STABLE #0: Mon Jan 30 11:08:39 BRT 20= 12 > root@Papi:/usr/src/sys/amd64/compile/LOBO =A0amd64 > > Had 4.1.8 when I red your post, went on and just finished compiling 4.1.1= 2. > > Up and running as I write. Hmmh. I wonder why I had the problem. As said, it was on AMD 64bit, FreeBSD-8-STABLE a few weeks ago, and I compiled 4.1.8. I used the gcc from the base system and did not have any make.conf entries. It was a "standard base" without any tweaks. I still have one 8.2-STABLE box with a kernel built on Jan 31. It is the identical twin of the box where I experienced the problem. I just run a portsnap and will see what happens if I try to build the newest VirtualBox. Takes a bit of time so may not come back until tomorrow (East Australian Time, it's afternoon here now) Regards Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAExkqpdCZNaRY%2Bn%2BQdm%2BbNpTwsDC1KjUo08d0%2BQ6tM-x2v%2B8jQ>