[QUICK] talloc bugs
Volker.Lendecke at SerNet.DE
Wed Jul 1 13:28:11 GMT 2009
On Wed, Jul 01, 2009 at 03:23:18PM +0200, Jelmer Vernooij wrote:
> > The shared library package maintainer might decide to change the major
> > version as a result, and that would be a perfectly valid reaction, but
> > to say we can't change code inside Samba is far too constraining on
> > the project.
> Changing the version number/soname should happen in the upstream
> project when the ABI is changed. This should also make sure we don't
> end up linking against outdated system versions of talloc.
How do you deal with libraries you link against that
themselves link in the system libs?
The example I had is libldap->libkrb5. That just broke all
the symbols I had carefully linked in statically into
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/samba-technical/attachments/20090701/423bc2e0/attachment.bin
More information about the samba-technical