REGISTER  


virtualbox start fails looking for libcap.so.1
This thread belongs to expert.forumgeeks.net


2009-01-16 13:39 GMT   |   #1
 
Slack12.2
I've found libcap-2.14 installed on this system but no lipcap.so.1
Anyone else seen this, have a hint?
2009-01-16 15:20 GMT   |   #2
 
If virtualbox insists in using "libcap.so.1" then set a symlink to
"libcap.so.2" (it should exist and should be a symlink to
libcap.so.2.14).

Then:

ldconfig

2009-01-20 19:20 GMT   |   #3
 
That's an UGLY solution, by the way. Generally speaking, you should
*never* symlink one major version of a shared library to another;
if the library developers are versioning them correctly, an incremented
major version number means that the API changed, and you might find
that whatever program you're using tries to use the new API in a manner
that won't work any more.

All that being said, I did the exact same thing on my system for VBox:

# ls -l /lib/libcap.*
-rw-r--r-- 1 root root 20K 2008-11-07 01:27 /lib/libcap.a
lrwxrwxrwx 1 root root 11 2008-11-07 11:05 /lib/libcap.so -> libcap.so.2
lrwxrwxrwx 1 root root 11 2009-01-20 17:24 /lib/libcap.so.1 -> libcap.so.2
lrwxrwxrwx 1 root root 14 2008-11-07 11:05 /lib/libcap.so.2 -> libcap.so.2.14
-rw-r--r-- 1 root root 15K 2008-11-07 01:27 /lib/libcap.so.2.14

I did that with the full knowledge that VBox could go tits-up, but it
was worth at least trying before working out how to make the "old"
libcap v1 coexist with libcap v2 (note that this might very well be
trivial to accomplish - I didn't bother with even checking, because
VBox works fine).

Again, though, this is almost *never* a *real* solution, and if you do
it haphazardly and without understanding the potential ramifications,
you WILL encounter problems sooner or later.
2009-01-21 17:20 GMT   |   #4
 
But remember that if you are a dedicated tinkerer, you will probably hose
your system some other way before the libraries collide hard enough to
scatter K-meson jets down the forward cone. And you can always hope that
by then Pat has released a new version and you'll have the perfect excuse
for a fresh install Smile
2009-01-22 23:20 GMT   |   #5
 
Valid points on all Wink

In my particular case, my VBox host isn't a "tinkerbox" at all - it's
the most powerful one in this house, and its sole purpose is to run
VirtualBox. As it turns out, the way that VBox uses the libcap library
makes it perfectly safe to do the symlink -- the ABI for *that* part
is the same in both libcap-1 and libcap-2. In even better news, it's
fixed in the new VBox 2.1.2 release - they no longer require the libcap
library at all.