Bug#871275: libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-08 Thread David Kalnischkies
On Tue, Aug 08, 2017 at 04:33:52PM -0400, James Cowgill wrote: > Maybe I misunderstood your question, but if you compile a library > exporting an affected conversion operator using GCC 7, GCC will emit an > alias to ensure that the old and new symbols both work. This is why *doh* You said it righ

Bug#871275: libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-08 Thread James Cowgill
Hi, On 08/08/17 15:44, David Kalnischkies wrote: > On Mon, Aug 07, 2017 at 03:47:15PM +0100, jcowg...@debian.org wrote: >> 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 co

Bug#871275: libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-08 Thread David Kalnischkies
On Mon, Aug 07, 2017 at 03:47:15PM +0100, jcowg...@debian.org wrote: > 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 t