Your message dated Mon, 10 Aug 2015 12:49:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#791216: netxx: library transition may be needed when
GCC 5 is the default
has caused the Debian Bug report #791216,
regarding netxx: library transition may be needed when GCC 5 is the default
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 [email protected]
immediately.)
--
791216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791216
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:netxx
Version: 0.3.2-2
Severity: important
Tags: sid stretch
User: [email protected]
Usertags: libstdc++-cxx11
Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI. Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols. If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.
What is needed:
- Rebuild the library using g++/g++-5 from experimental. Note that
most likely all C++ libraries within the build dependencies need
a rebuild too. You can find the log for a rebuild in
https://people.debian.org/~doko/logs/gcc5-20150701/
Search for "BEGIN GCC CXX11" in the log.
- Decide if the symbols matching __cxx11 or B5cxx11 are part of the
library API, and are used by the reverse dependencies of the
library.
- If there are no symbols matching __cxx11 or B5cxx11 in the symbols
forming the library API, you should close this issue with a short
explanation.
- If there are no reverse dependencies, it should be the package
maintainers decision if a transition is needed. However this might
break software which is not in the Debian archive, and built
against these packages.
- If a library transition is needed, please prepare for the change.
Rename the library package, append "v5" to the name of the package
(e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
have a soversion bump and you upload this version instead of the
renamed package. Prepare a patch and attach it to this issue (mark
this issue with patch), so that it is possible to NMU such a
package. We'll probably have more than hundred transitions
triggered. Then reassign the issue to release.debian.org and
properly tag it as a transition issue, by sending an email to
[email protected]:
user [email protected]
usertag <this issue> + transition
block <this issue> by 790756
reassign <this issue> release.debian.org
- If unsure if a transition is needed, please tag the issue with help
to ask for feedback from other Debian developers.
The libstdc++6 transition will be a large one, and it will come with a
lot of pain. Please help it by preparing the follow-up transitions.
[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
On Fri, Jul 3, 2015 at 13:13:05 +0000, Matthias Klose wrote:
> - Rebuild the library using g++/g++-5 from experimental. Note that
> most likely all C++ libraries within the build dependencies need
> a rebuild too. You can find the log for a rebuild in
> https://people.debian.org/~doko/logs/gcc5-20150701/
> Search for "BEGIN GCC CXX11" in the log.
>
> - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
> library API, and are used by the reverse dependencies of the
> library.
>
The log shows:
000000000000b6d0 w DF .text 0000000000000171 Base
_ZNSt7__cxx114listISt4pairIiPKN5Netxx9ProbeInfoEESaIS6_EEaSERKS8_
0000000000009b60 w DF .text 0000000000000055 Base
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev
000000000000c3f0 w DF .text 0000000000000151 Base
_ZNSt7__cxx114listIiSaIiEEaSERKS2_
000000000000b560 w DF .text 0000000000000161 Base
_ZNSt7__cxx114listISt4pairIijESaIS2_EEaSERKS4_
0000000000009e60 w DF .text 00000000000003c9 Base
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS5_S7_EERKS5_
0000000000009b60 w DF .text 0000000000000055 Base
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev
000000000000c550 w DF .text 0000000000000099 Base
_ZNSt7__cxx114listIiSaIiEE6removeERKi
As far as I can tell none of these are symbols from netxx, they look
like instantiations of libstdc++ templates.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
