Bug#681475: marked as done (std::pair C++03/11 incompat)
Your message dated Sat, 14 Jul 2012 03:04:46 +0200
with message-id <5000C5AE.3060200@debian.org>
and subject line Re: Bug#681475: std::pair C++03/11 incompat
has caused the Debian Bug report #681475,
regarding std::pair C++03/11 incompat
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.)
--
681475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681475
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.7
Version: 4.7.1-2
In the current version of GCC 4.7 in Debian, std::pair isn't
ABI-compatible when used as a return value between C++03 and C++11 modes.
This was recently fixed in:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53657
It'd be really nice to get the fixed version of gcc accepted into wheezy,
so that users (or packages) compiling with -std=c++11 don't get mysterious
crashes from it. This particular incompatibility bites many boost::python
programs compiled in C++11 mode (against the c++03 debian
libboost-python), and surely there are other real cases where it shows up
as well.
--- End Message ---
--- Begin Message ---
tags 681475 + sid wheezy upstream
severity 681475 serious
thanks
Version: 4.7.1-5
On 13.07.2012 15:21, James Y Knight wrote:
> Package: gcc-4.7
> Version: 4.7.1-2
>
> In the current version of GCC 4.7 in Debian, std::pair isn't
> ABI-compatible when used as a return value between C++03 and C++11 modes.
> This was recently fixed in:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53657
>
> It'd be really nice to get the fixed version of gcc accepted into wheezy,
> so that users (or packages) compiling with -std=c++11 don't get mysterious
> crashes from it. This particular incompatibility bites many boost::python
> programs compiled in C++11 mode (against the c++03 debian
> libboost-python), and surely there are other real cases where it shows up
> as well.
fixed in 4.7.1-5
--- End Message ---
Reply to: