Is there a workaround for this bug, while waiting for gcc 4.8 to get
fixed? Holding libstdc++6 back tends to break stuff.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Matthias,
Please could you name the software where you did see this failure?
I only spotted this regression in my own development code, so it seems
that the impact is limited after all.
Thanks,
Tim
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: libstdc++6
Version: 4.8.0-8
Severity: important
Dear Maintainer,
Attached test case gets the current system time using std::chrono and using
gettimeofday, both with millisecond precision. Using libstdc++6 version 4.8.0-7,
this code works properly, both timestamps being identical.
This also seems to apply to already-compiled binaries, e.g. if I compile the
aforementioned testcase with libstdc++6 version 4.8.0-7, which results in
correct output, and then upgrade libstdc++6 to version 4.8.0-8, re-running the
testcase without recompilation results in faulty output.
So since
Am 29.05.2013 09:39, schrieb Tim Besard:
Package: libstdc++6
Version: 4.8.0-8
Severity: important
Dear Maintainer,
Attached test case gets the current system time using std::chrono and using
gettimeofday, both with millisecond precision. Using libstdc++6 version
4.8.0-7,
this code
Am 29.05.2013 16:09, schrieb Matthias Klose:
So first lets see which packages are affected, then decide how to address this
(currently searching the Ubuntu archive for these symbols, lacking the
resources
to do that for the Debian archive). You only see this in c++0x/c++11 mode, so
this
6 matches
Mail list logo
