Date: Thu, 12 Dec 2013 17:35:55 +0100 From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= <mikael.urankar@gmail.com> To: "freebsd-emulation@freebsd.org" <freebsd-emulation@freebsd.org> Subject: Re: [Call for Testers] VirtualBox 4.3.2 : Success Message-ID: <CAJwjRmSen48UEiuFO2=1Hb2B8AM7U9MATQR_ACDXV-Lc-sVL%2Bg@mail.gmail.com> In-Reply-To: <CAE-m3X3uNzcF4_1x3G=tM2r72HRR9d3vtBKsM3ay7HUK0Te3%2Bw@mail.gmail.com> References: <CAJwjRmRUkmuHRZ-CKQH73=j2s0dY-=diBKS%2B5GnjV5TM2yE41w@mail.gmail.com> <CAE-m3X3uNzcF4_1x3G=tM2r72HRR9d3vtBKsM3ay7HUK0Te3%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2013/12/12 Bernhard Fr=C3=B6hlich <decke@freebsd.org>:
> Could you please do "ldd /usr/local/bin/VirtualBox" and send me the
> output? I have
> just committed a fix to the vbox 4.2.20_1 port that fixes an issue
> where vbox picks up
> incompatible libstdc++ and other shared objects which cause it to fail
> in strange ways
> (sometimes directly at startup or even at runtime). It could be that
> this bug is also
> because of that.
>
> You could try to install vbox 4.2.20_1 and see if that works or fails the=
same.
Here are the results:
/usr/local/bin/VirtualBox:
libthr.so.3 =3D> /lib/libthr.so.3 (0x800821000)
libstdc++.so.6 =3D> /usr/local/lib/gcc46/libstdc++.so.6 (0x800a4600=
0)
libm.so.5 =3D> /lib/libm.so.5 (0x800d4a000)
libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x800f70000)
libc.so.7 =3D> /lib/libc.so.7 (0x80117d000)
vbox 4.2.20_1 works fine, thanks!
I've noticed this problem on misc/qt4-qtdemo, the first time it was
built with clang and worked just fine, the second time with GCC (I've
put USE_GCC=3D 4.6 in the Makefile) and one of the qt4-demo (I haven't
tested them all) crashed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJwjRmSen48UEiuFO2=1Hb2B8AM7U9MATQR_ACDXV-Lc-sVL%2Bg>