Home/ Questions/Q 64009
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T18:43:21+00:00

I have a library A, that I develop. When I deploy it on a

  • 0

I have a library A, that I develop. When I deploy it on a machine, the corresponding libA.so and libA-X.Y.Z.so are put in /usr/lib (X.Y.Z being the version number).

Now I develop a library B, which uses A. When I link B, I use the flag -lA. Then ‘ldd libB.so‘ gives me : 

(...) libA-X.Y.Z.so => /usr/lib/libA-X.Y.Z.so (...)

My problem is that when I release a new version of A (X.Y.ZZ), I also have to release a new version of B. Otherwise, someone installing the latest A won’t be able to install B which will be looking for the version X.Y.Z which doesn’t exist.

How do I solve this problem ? How can I tell B to look for libA.so and not libA-X.Y.Z.so ? Or is it wrong to do so ? even unsafe ?

Update 1 : library A (that I inherited from someone else) uses autotools.

Update 2 : when I build library A, I can see : ‘-Wl,-soname -Wl,libA-0.6.1.so’. If I understand properly that means that we are forcing the soname to be libA-0.6.1.so. Is that right ? Now my problem is that I have no clue how to modify this behaviour in a project which uses autotools. I googled for a while but can’t find any useful information. Should I modify configure.in or a Makefile.am ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. When you create libA.so, pass the -soname option to the linker (if you linking through gcc, use -Wl,-soname). Then, when B gets linked, the linker refers to A through its soname, not through its filename. On the target system, make sure you have a link from the soname to the real file. See

    http://www.linux.org/docs/ldp/howto/Program-Library-HOWTO/shared-libraries.html

    • 0