Bug#793244: git-crypt: change of type in system_error might break with GCC-5
Control: found 793244 0.5.0-1 Control: fixed 793244 0.7.0-0.1 Control: close 793244 X-Debbugs-CC: a...@andrewayer.name d...@debian.org On Wed, 22 Jul 2015 13:33:34 + Matthias Klose wrote: > Package: src:git-crypt > Severity: important > Tags: sid stretch > User: debian-...@lists.debian.org > Usertags: gcc-pr66145 > > GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed > upstream in time for the GCC defaults change. The work around is to > rebuild the affected packages after GCC 5 is the default compiler. > Please look at the code and decide, if the package is affected. If > not, please just close the issue. If it's a real issue, I'll add > the packages affected to libstdc++6's Breaks attributes, with the > version of the package at the time of the defaults change. > > See https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29 > for further information. > > To build with GCC 5,install the gcc, g++, gfortran, ... packages > from experimental (apt-get -t experimental install g++). With the GCC 5 transition completed long long ago, I believe at least the most recent upload in Sid is not affected by GCC's change. Closing this bug accordingly. If there are anything that I'm missing, please feel free to make corrections. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#793244: git-crypt: change of type in system_error might break with GCC-5
On 07/22/2015 08:05 PM, Andrew Ayer wrote: tags 793244 + confirmed thanks On Wed, 22 Jul 2015 13:33:34 + Matthias Klose d...@debian.org wrote: GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed upstream in time for the GCC defaults change. The work around is to rebuild the affected packages after GCC 5 is the default compiler. Please look at the code and decide, if the package is affected. If not, please just close the issue. If it's a real issue, I'll add the packages affected to libstdc++6's Breaks attributes, with the version of the package at the time of the defaults change. I've confirmed that git-crypt is affected. However, are you sure that rebuilding is a sufficient workaround? When I tried building with g++ 5.2.1-11 from experimental, I had to use -D_GLIBCXX_USE_CXX11_ABI=0 in order to successfully catch std::ios_base::failure. Should I modify git-crypt to build with this flag? no, that was an omission in libstdc++6, now fixed in 5.2.1-12. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793244: git-crypt: change of type in system_error might break with GCC-5
tags 793244 + confirmed thanks On Wed, 22 Jul 2015 13:33:34 + Matthias Klose d...@debian.org wrote: GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed upstream in time for the GCC defaults change. The work around is to rebuild the affected packages after GCC 5 is the default compiler. Please look at the code and decide, if the package is affected. If not, please just close the issue. If it's a real issue, I'll add the packages affected to libstdc++6's Breaks attributes, with the version of the package at the time of the defaults change. I've confirmed that git-crypt is affected. However, are you sure that rebuilding is a sufficient workaround? When I tried building with g++ 5.2.1-11 from experimental, I had to use -D_GLIBCXX_USE_CXX11_ABI=0 in order to successfully catch std::ios_base::failure. Should I modify git-crypt to build with this flag? Thanks, Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
