Freeimage 3.10 -> 3.17 upgrade, dealing with library incompatibility

[Florian Weimer]

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?

-- 
Florian Weimer / Red Hat Product Security