[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#871273: marked as done (libabigail0: requires rebuild against GCC 7 and symbols/shlibs bump)



Your message dated Mon, 07 Aug 2017 15:19:18 +0000
with message-id <E1dejoM-0007am-1q@fasolo.debian.org>
and subject line Bug#871273: fixed in libabigail 1.0~rc6-2
has caused the Debian Bug report #871273,
regarding libabigail0: 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 owner@bugs.debian.org
immediately.)


-- 
871273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871273
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libabigail0
Version: 1.0~rc6-1
Severity: serious
Tags: sid buster
User: debian-gcc@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 ---
Source: libabigail
Source-Version: 1.0~rc6-2

We believe that the bug you reported is fixed in the latest version of
libabigail, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871273@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated libabigail package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 07 Aug 2017 10:58:04 -0400
Source: libabigail
Binary: libabigail-dev libabigail0 abigail-tools abigail-doc
Architecture: source
Version: 1.0~rc6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Description:
 abigail-doc - ABI Generic Analysis and Instrumentation Library (documentation)
 abigail-tools - ABI Generic Analysis and Instrumentation Library (tools)
 libabigail-dev - ABI Generic Analysis and Instrumentation Library (development fil
 libabigail0 - ABI Generic Analysis and Instrumentation Library (runtime)
Closes: 871273
Changes:
 libabigail (1.0~rc6-2) unstable; urgency=medium
 .
   * Bump standards version.
   * Build using GCC 7 and tighten dependency on the shared library.
     Closes: #871273.
Checksums-Sha1:
 6bbf38446a6b443a1257e13268187c42a0bebaa6 2267 libabigail_1.0~rc6-2.dsc
 865d9ca8a1b2572c6bb2c0f571b7d043ef412e46 3508 libabigail_1.0~rc6-2.debian.tar.xz
 3826a48d642232120c904709b0c945de4c61aead 9473 libabigail_1.0~rc6-2_source.buildinfo
Checksums-Sha256:
 417e45307b2e4bcc45c2c6f948af833ef01a4eea85bd980bc2078ce89bdf2885 2267 libabigail_1.0~rc6-2.dsc
 91cf19a4a22884ef62910a443fb59af3b99dcec9ac7e1e5d35ca30a614986278 3508 libabigail_1.0~rc6-2.debian.tar.xz
 6df92ddf41e5f5428c9c67f3a31e99f3cc6514bf0aaa4e5d4617c2730a268ba8 9473 libabigail_1.0~rc6-2_source.buildinfo
Files:
 5b0d663af35ceaac9464334e1d3f1c22 2267 libs optional libabigail_1.0~rc6-2.dsc
 64e70df886e43974e366b4272d9e73f6 3508 libs optional libabigail_1.0~rc6-2.debian.tar.xz
 0e277f5c7100b78811ec27e2feadb882 9473 libs optional libabigail_1.0~rc6-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlmIgSsQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9XzuD/9gFlAfgdgXJrtkX3U1rgGjdXKJ4IWdw3KE
weRpMju5O03zHTLaGSTwCitbYvvv0Uj63TO0J/T1NolWRwTLoRx69TDS/qLDRxWZ
VTcMC7JT8KqEQwBlYDBNv+UI2DKLzNfiCDaEuq4KsSY7ulsJbkKAc0DbUOGMKatq
63Ky0St7Go8WO2yXyYxnmSAqHC/nY3nDdDiwX9CyIlxMHWW9geBKUopo9jJyz4YF
PYEVMY8PvLR5hN1yF4uwXIjey1Ox+jIpS0GIeqv2yjGzNeVvU6Ht5QzHVDbdVz0n
TSH5DfjfYnza6tMFDNH/DQhjEe7ENlUNVm5xCelwgaAF/6WZaYahv9lvrqxiw+dO
N6LSpQzp9msg5PgmFR3Md4wJ9uVG9EHv8SgXNIC9YqHfFB4iEZBRzuSi0urXOPwk
v+CBiAEVL1qKh27mHVM6hwjHr76jr2wazIXG0H8NBlKRcnroBIclwrRy16QqFVXc
J1CKBdRJNwuTEkqxrvHDbxAOKURwLHAGYI1R1/SVtIU4nej+R+5elM1m2A8rmHE5
CEuYWgoqqajuFKihC/YSjkFuyWq1DX6NjZaGsIGwQh8vPAFCkNXHy3baEUue+w0t
66lKIE+ILWzD5SOAKGpUizLq0On3322o38MlAO5SADv5Tv69eJ0E1Iiwwh+nfQBR
jvr2P89jLg==
=/Aov
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: