[Bug 675946] Re: libicu is not ABI compatible because of --enable-renaming usage

[Dmitrijs Ledkovs]

Based on
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/675946/comments/5
this is desired behaviour.

** Summary changed:

- libicu is not ABI compatible
+ libicu is not ABI compatible because of --enable-renaming usage

** Changed in: icu (Ubuntu)
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/675946

Title:
  libicu is not ABI compatible because of --enable-renaming usage

Status in “icu” package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: libicu42

  Currently, libicu is built with symbol renaming, which leads to a rename of
  every symbol, e.g. ucol_strcoll becomes ucol_strcoll_4_2. Check with "nm -CD
  libicui18n.so.42" - all public symbols have the _4_2 suffix.

  This means that on the next system upgrade (e.g. to libicu 4.4), all
  applications linking to libicu will need to be rebuilt.

  For reference, see
  http://userguide.icu-project.org/design#TOC-ICU-Binary-Compatibility:-Using-ICU

  Quoting:

  ========
  To enable release-to-release binary compatibility, ICU must be built with
  --disable-renaming, and applications must be built using the headers and
  libraries that resulted from the –-disable-renaming ICU build
  ========

  I suggest to follow ICU's suggestion to build libicu with --disable-renaming, so the library can be
  upgraded without breaking binary compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/675946/+subscriptions