VirtualBox errors when I try to run (dlopen("/usr/local/lib/virtualbox/VBoxRT.so", ))

[Bernhard Fröhlich]

Am 08.12.2013 20:15 schrieb "Mark Felder" <feld at freebsd.org>:
>
>
>
> On Sat, Dec 7, 2013, at 2:02, Bernhard Fröhlich wrote:
> > Am 06.12.2013 23:24 schrieb "Eitan Adler" <lists at eitanadler.com>:
> > >
> > > On Fri, Dec 6, 2013 at 4:04 PM, Bernhard Fröhlich <decke at bluelife.at>
> > wrote:
> > > >
> > > > Am 06.12.2013 21:45 schrieb "Eitan Adler" <lists at eitanadler.com>:
> > > >
> > > >
> > > >>
> > > >> I get the following when try to run VirtualBox.
> > > >>
> > > >> VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
> > > >> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed:
> > > >> /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15
required
> > > >> by /usr/local/lib/virtualbox/VBoxRT.so not found
> > > >>
> > > >> %pkg info -x compat9x
> > > >> compat9x-amd64-9.2.902000.201310
> > > >> %pkg info -x virtualbox
> > > >> virtualbox-ose-4.2.18_1
> > > >> virtualbox-ose-kmod-4.2.18
> > > >>
> > > >> Any ideas how for to fix this?
> > > >
> > > > Deinstall the compat port(s) and it will work again.
> > >
> > > I need the compat port for Java.  Is it possible to have VirtualBox
> > > ignore the compat libs? why is it looking their anyway?
> >
> > I think it's a similar problem as described in ports/182468 and for some
> > reason rtld seems to pickup libs from compat which might be correct in
> > general but it's causing problems for us.
> >
>
> We discussed this in IRC the other day, Bernard. Look at the rpath (
> readelf -d )of /usr/local/lib/virtualbox/VBoxRT.so -- it's wrong. It's
> only listing /usr/local/lib/virtualbox.
>
> /usr/ports/emulators/virtualbox-ose > make -V LDFLAGS
>  -Wl,-rpath=/usr/local/lib/gcc46
>
> Why aren't the virtualbox binaries ignoring those LDFLAGS?

Could you describe your proposal a bit more precisely? Vbox has a rpath
config variable that we can tune a bit. I am not sure yet if this is a bug
in the vbox build framework or the ports framework is doing something
stupid or the mess in 10 is triggering that.