Is there any particular reason why shared objects are built+named in the following manner? somelib.so.X.a.b.c somelib.so.X --> somelib.so.X.a.b.c somelib.so --> somelib.so.X.a.b.c Most of the .X.a.b.c do not follow the library's version and instead appear to be random. --mmadia