Your message dated Wed, 21 Aug 2013 12:01:26 +0200 with message-id <[email protected]> and subject line Re: Bug#718453: libstdc++6-4.7-dev: condition_variable fails to compile when building with clang has caused the Debian Bug report #718453, regarding libstdc++6-4.7-dev: condition_variable fails to compile when building with clang 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.) -- 718453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718453 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libstdc++6-4.7-dev Version: 4.7.2-5 Severity: important Dear Maintainer, The following code compiles with gcc, but fails to compile with clang. $ cat /tmp/test.cc #include <condition_variable> $ clang --version Debian clang version 3.4-1 (trunk) (based on LLVM 3.4) Target: x86_64-pc-linux-gnu Thread model: posix $ clang -std=c++11 /tmp/test.cc In file included from /tmp/test.cc:1: In file included from /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/condition_variable:38: /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/chrono:540:6: error: no matching constructor for initialization of 'duration' (aka 'std::chrono::duration<long, std::ratio<1, 1000000> >') : __d(__t.time_since_epoch()) ^ ~~~~~~~~~~~~~~~~~~~~~~ /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/condition_variable:111:42: note: in instantiation of function template specialization 'std::chrono::time_point<std::chrono::system_clock, std::chrono::duration<long, std::ratio<1, 1000000> > >::time_point<std::chrono::duration<long, std::ratio<1, 1000000000> > >' requested here const __clock_t::time_point __s_atime = __s_entry + __delta; ^ /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/chrono:234:12: note: candidate constructor not viable: no known conversion from 'duration<[...], ratio<[...], 1000000000>>' to 'const duration<[...], ratio<[...], 1000000>>' for 1st argument constexpr duration(const duration&) = default; ^ /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/chrono:240:23: note: candidate template ignored: couldn't infer template argument '' constexpr explicit duration(const _Rep2& __rep) ^ /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/chrono:247:14: note: candidate template ignored: couldn't infer template argument '' constexpr duration(const duration<_Rep2, _Period2>& __d) ^ /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/chrono:232:12: note: candidate constructor not viable: requires 0 arguments, but 1 was provided constexpr duration() : __r() { } ^ 1 error generated. $ gcc -std=c++11 /tmp/test.cc /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/crt1.o(.text+0x20): error: undefined reference to 'main' collect2: error: ld returned 1 exit status Upstream seems to have fixed the problem. Can the upstream fix be applied here? http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53841 Extra packages (build from source from unstable.) ii clang-3.4 1:3.4~svn183914-1 -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libstdc++6-4.7-dev depends on: ii g++-4.7 4.7.2-5 ii gcc-4.7-base 4.7.2-5 ii libc6-dev 2.13-38 ii libstdc++6 4.7.2-5 libstdc++6-4.7-dev recommends no packages. Versions of packages libstdc++6-4.7-dev suggests: pn libstdc++6-4.7-doc <none> -- no debconf information
--- End Message ---
--- Begin Message ---Version: 4.7.3-1 Am 01.08.2013 00:45, schrieb Austin Schuh: > Package: libstdc++6-4.7-dev > Version: 4.7.2-5 > > Upstream seems to have fixed the problem. Can the upstream fix be applied > here? > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53841
--- End Message ---
