On 2025-10-27 Matthew Vernon <[email protected]> wrote: > Hi, > If you have a look at the upstream issue:
> https://github.com/PCRE2Project/pcre2/issues/832 > There is clearly some confusion about symbol versioning & soname changes; if > you are knowledgable about this topic (I'm not!), would you mind shedding > some light there, please? Hello, adding symbol-versioning does not actually break the ABI, but there can be warning messages if the distribution's dependency system does not enforce that packages built against pcre-symver cannot be installed/run with (old) pcre-no-symver: Running a binary built against pcre-symver with pcre-no-symver results in: | [binaryname]: /lib/x86_64-linux-gnu/libpcre2-8.so.0: no version information available (required by [binaryname]]) There is no warning message for binaries built against the older pcre-no-symver being run against pcre-symver. In Debian we can enforce this and avoid the warnings. I think rpm-based distributions should be fine too with the type of symbol versioning chosen by pcre2. Do not know about the others. (Afaict the issues reported upstream bug-report have all been diagnosed as not being related to symbol-versioning) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
