Your message dated Tue, 12 Sep 2017 22:09:53 +0200
with message-id <20170912200953.s5fqobv5qmlea...@i5.cruise.homelinux.net>
and subject line Re: Bug#871276: kopano-libs: requires rebuild against GCC 7
and symbols/shlibs bump
has caused the Debian Bug report #871276,
regarding kopano-libs: requires rebuild against GCC 7 and symbols/shlibs bump
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
871276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kopano-libs
Version: 8.1.0-3
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling
Hi,
It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling
In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.
To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
conversion operator symbols have a version matching the version this
bug is fixed in (including the Debian revision and tilde if
necessary).
Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >[abi:cxx11]()@APTPKG_5.0" 0.8.0
+ (c++)"URI::operator std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >()@APTPKG_5.0" 1.5~beta2~
Where "1.5~beta2" is the version this bug was fixed in.
- If your package does not provide a symbols file, add a dh_makeshlibs
override so that tight enough dependencies are generated.
Using libebml as an example (debian/rules):
+ override_dh_makeshlibs:
+ # For new symbols when compiled with GCC 7
+ dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
Where "1.3.4-2" is the version this bug was fixed in.
- If your package is about to be renamed due to an upstream SONAME bump,
you do not need to add any special symbols handling.
If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.
Thanks,
James
--- End Message ---
--- Begin Message ---
Version: 8.3.3-1
This issue was solved with the a prepared version 8.3.2-1 which never
hitted the archive due a upload of a more recent version 8.3.3-1 which
needed to go through in NEW.
(Re-send because of misspelled closing address ...)
On Mon, Aug 07, 2017 at 03:47:15PM +0100, jcowg...@debian.org wrote:
> Package: kopano-libs
> Version: 8.1.0-3
> Severity: serious
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: gcc-7-op-mangling
>
> Hi,
>
> It appears that your package provides an external symbol that is
> affected by the recent name mangling changes in GCC 7. See:
> https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling
>
> In GCC 7, the name mangling for C++ conversion operators which return a
> type using the abi_tag attribute (most commonly std::string) has
> changed. When your library is compiled with GCC 7, it will now emit two
> symbols for the conversion operator using the new and old naming.
> Executables compiled with GCC 7 will always use the new symbol, while
> old executables compiled using <= GCC 6 will use the old symbol. For new
> executables to build without undefined references, your library will
> need rebuilding with GCC 7.
>
> To ensure that new executables will pull in the newer version of the
> library built with GCC 7:
> - Your library package should Build-Depend on g++ (>= 4:7).
> - If your package provides a symbols file, ensure that the new
> conversion operator symbols have a version matching the version this
> bug is fixed in (including the Debian revision and tilde if
> necessary).
>
> Using apt as an example (debian/libapt-pkg5.0.symbols):
> (c++)"URI::operator std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> >[abi:cxx11]()@APTPKG_5.0" 0.8.0
> + (c++)"URI::operator std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> >()@APTPKG_5.0" 1.5~beta2~
>
> Where "1.5~beta2" is the version this bug was fixed in.
>
> - If your package does not provide a symbols file, add a dh_makeshlibs
> override so that tight enough dependencies are generated.
>
> Using libebml as an example (debian/rules):
> + override_dh_makeshlibs:
> + # For new symbols when compiled with GCC 7
> + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
>
> Where "1.3.4-2" is the version this bug was fixed in.
>
> - If your package is about to be renamed due to an upstream SONAME bump,
> you do not need to add any special symbols handling.
>
> If you would like to know the exact name of the new symbols, using
> "abipkgdiff" from abigail-tools might be able to help.
>
> Thanks,
> James
--- End Message ---
