![](https://seccdn.libravatar.org/avatar/e1ad78837291ae9e0ef67a01d37bec8d.jpg?s=120&d=mm&r=g)
On Fri, 21 Nov 2008 10:35:08 +0100, you wrote:
Despite appearances, I think we are saying sort of the same thing.
I dont't think so.
I mentioned that the SVR4 lib tools allowed one to set this explicitly.
I guess you mean the name that gets recorded in the binary?
I am not sure how it gets set with the gcc tools.
You set the soname of a library with the -soname= option for ld. If you don't give one explicitly, it will, AFAIR, be the file name of the library.
The various Makefiles for libs do it differently. Some make a libX.so and make links to it for the libX.so.MAJ.min files. Some make a libX.so.MAJ and link to get the libX.so and libX.so.MAJ.min. All will have different soname in their libraries.
The soname that get's recorded in a binary does not depend on the symlink but rather what got recorded in the DT_SONAME field of the shared object (i.e. library)! Example: libfoo.so.1.2.3 has an soname of libfoo.so.1 No matter what the symlink libfoo.so points to, the binary linked with this library will always require libfoo.so.1.
Of course Shared_Library_Packaging_Policy is about packaging and not building. You must supply all the variant names of a file to cover all bases.
No, you use only one name and that is based on the soname as hardcoded in the shared library. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org