Freeimage 3.10 -> 3.17 upgrade, dealing with library incompatibility

[Sandro Mani]

On 17.09.2015 10:46, Florian Weimer wrote:
> On 09/17/2015 10:28 AM, Sandro Mani wrote:
>
>> - abi_compliance_checker reports that compatibility was not broken
>> between libfreeimage of 3.10 and 3.17. However, in libfreeimageplus,
>> various function signatures have changed due to switching from WORD (aka
>> unsigned short) to unsigned for various size related parameters. The
>> soname was not changed, so this is an upstream error.
> Why doesn't abi_compliance_checker report this?  Doesn't such a
> modification change the list of exported symbols due to C++ name mangling?
>
Uh guess didn't express this very clearly: it does not report 
incompatibilities on the libfreeimage library, but it does report them 
on libfreeimageplus library.

(i.e. libfreeimage referring to that actual library, not the entire 
package).