Hi,
I just stumbled across this issue. As clang-3.2 certainly doesn't have
any chance of making it into this release anymore, shouldn't this bug be
reopened and assigned to libstdc++6-4.7? A one-line fix seems more
likely to still make it into the release.
I'd also be in favor of severity: import
On the clang page there is said
"Patches are needed to make libstdc++-4.4
(http://clang.llvm.org/libstdc++4.4-clang0x.patch) and libstdc++-4.7
(http://clang.llvm.org/libstdc++4.7-clang11.patch) work with Clang in
C++11 mode." (http://clang.llvm.org/cxx_status.html)
There is also a bug-report on cl
Hello Mario,
>
> x4:/tmp% clang++ -std=c++0x -o clang-chrono clang-chrono.cxx
> In file included from clang-chrono.cxx:1:
> /usr/include/c++/4.6/chrono:666:7: error: static_assert expression is not an
> integral constant expression
> static_assert(system_clock::duration::min()
> ^
Package: clang
Version: 3.0-6
Severity: normal
Dear Maintainer,
clang fails to include chrono from C++11.
Here is a minimal example program:
--
#include
int main() { }
--
Building with GCC (4.6 and 4.7) works fine:
x4:/tmp% g++-4.6 -std=c++0x -o clang-chrono clang-chrono.cxx
x4:/tmp%
4 matches
Mail list logo
