Solaris

Does anyone know whether it is possible to make self contained shared libraries ? (.so files). If so, what is the way to do it ?

---------- Post updated at 08:03 AM ---------- Previous update was at 07:56 AM ----------

On Solaris that is.

Please define what you mean by self contained.

I get a different behavior on a Solaris machine were the application is deployed, than on the machine were it was compiled, linked and tested.
I thought that if it was possible to link together an .so that no external references remain, in the sense that not any other .so is loaded at run time (everything needed is already contained in the one single .so file), it would behave in the same way.
So why not link statically (.a) ??
It is a Java C-native library (c code called from Java), and hence it has to be a shared object.

That's not the usual meaning of self contained library which is libraries that have their runpath correctly configured.

I see.
But do you understand my concern ?
If so, is there a way to achieve what I am after ?

You'd have to find static libraries to link to instead of shared ones.

And that may cause duplicate symbol errors when you actually use it.

It will also make the resulting library enormous.

You'd rather explain better what is the precise problem you are trying to solve with self contained libraries.

Outside "different behavior", you didn't provide any details or clues.