On Feb 05, Simon Josefsson <si...@josefsson.org> wrote: > > The problem is that this is not enough to make the built binaries work > > on stable again[1] because upstream gratuitously broke the ABI in 1.13 > > by versioning the symbols and now it is too late to revert the change. > The symbols are the same, so the ABI should be both forward and > backwards compatible. See my discussion about a similar issue in: They are not the same, since the old ones are unversioned. I know well that "it's just a warning", but the warning means that distributions now must treat this as an ABI change and binaries built with new new library must depend on it. Since having programs spewing warnings on startup is bad and will often also break things (think e.g. a daemon run by inetd), for all practical purposes you effectively broke the ABI (and without any benefit even!).
> > I suppose that there is some way to generate both versioned and > > unversioned symbols with appropriate linker magic, but I have not been > > able to do it. > That happens by default. Tools linked with versioned libraries will get It does not, or we could link programs and libraries with unversioned symbols and forget about versioned symbols until they will actually be needed. > a warning with (dynamically) linked to un-versioned libraries, though, > but that is not really an ABI issue as far as I can tell. It is a > problem in the binary that is linked to libgsasl. This happens with everything, not only libraries. -- ciao, Marco
signature.asc
Description: Digital signature
