Bug#772122: libclang-common-3.5-dev: x86_64 clang does not ship i386 asan libraries for -m32 compilation

2014-12-05 Thread Tim Besard
Package: libclang-common-3.5-dev Version: 1:3.5-6 Severity: normal Dear Maintainer, Trying to use the address sanitizer, with -m32 on a x86_64 platform, but clang complains about missing files: $ clang -fsanitize=address -m32 /dev/null /usr/bin/ld: cannot find

Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-06-07 Thread Tim Besard
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

Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-05-30 Thread Tim Besard
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

Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-05-29 Thread 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 works properly, both timestamps being identical.

Bug#710220:

2013-05-29 Thread Tim Besard
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

Bug#698715: mumble-server: Failure to start when using MySQL database

2013-01-22 Thread Tim Besard
Package: mumble-server Version: 1.2.3-349-g315b5f5-2.2 Severity: important Dear Maintainer, When using mumble-server in combination with a dedicated MySQL database, rather than the built-in sqlite one, the daemon fails to start with the following error: F2013-01-22 17:53:31.948 ServerDB: