>> So no, no minor revision gets encoded into the SONAME.
>
> Then what's the significance of the .1.0 at the end of the SONAME? Is
> it just nipples for men? (I hope no one objects to my extending the
> Monty Python theme to Time Bandits).
Some systems require that shared libraries have a vers
On Mar 24, 2:23 pm, "Martin v. Löwis" wrote:
> > So, for example, if I upgrade to libpython2.6.so.1.1
>
> How do you do that? There won't ever be such a library. They
> will always be called libpython2.6.so.1.0.
>
> So no, no minor revision gets encoded into the SONAME.
Then what's the significan
> So, for example, if I upgrade to libpython2.6.so.1.1
How do you do that? There won't ever be such a library. They
will always be called libpython2.6.so.1.0.
So no, no minor revision gets encoded into the SONAME.
Regards,
Martin
--
http://mail.python.org/mailman/listinfo/python-list
I'm wondering why the SONAME in libpython.so has a minor revision
encoded in it; for example (on Linux):
$ readelf -d libpython2.6.so | grep SONAME
0x000e (SONAME) Library soname:
[libpython2.6.so.1.0]
Because of this, if I compile an app against this library (with '-L/
u
