A linker problem with a couple of library needed by VirtualBox

crisostomo_enrico · 09-12-2008, 07:31 PM

Hi.

I just installed VirtualBox 2.0.2 on OpenSolaris and when I launched it it complained about unresolved libraries:

Code:

ld.so.1: VirtualBox: fatal: libstdc++.so.6: open failed: No such file or directory

A check with ldd indeed detected that both libstdc++.so.6 and libgcc_s.so.1 were not found. I then exported LD_LIBRARY_PATH:

Code:

export LD_LIBRARY_PATH=/usr/sfw/lib/amd64

and to my surprise ldd continued not to find the libraries! I solved the problem creating a soft link to both libraries in VirtualBox installation directory but cannot explain the dynamic linker behavior.

Any hint about this?
Thanks,
Enrico

bathory · 09-13-2008, 11:09 AM

You can use "crle" to add more library directories to the defaults.
Take a look at the manpage of crle, or at this quick tutorial.

Regards

crisostomo_enrico · 09-14-2008, 02:28 PM

Thank you bathory, I didn't know this command and it seems to be very useful, indeed. I just added it to my tool box.

Nevertheless, my curiosity about why setting LD_LIBRARY_PATH fails to work is still there.

bathory · 09-14-2008, 05:54 PM

Quote:

Originally Posted by crisostomo_enrico

Nevertheless, my curiosity about why setting LD_LIBRARY_PATH fails to work is still there.

I guess this happens because the program was compiled using the -R linker option, which according to Sun is the correct way to build s/w.

crisostomo_enrico · 09-14-2008, 06:43 PM

Thank you another time, bathory. The explanation I found on the link you posted is indeed satisfactory.

Bye,
Enrico.