Date: Thu, 08 Dec 2016 07:03:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 215138] devel/libc++ + lang/gcc: #error <atomic> is not implemented Message-ID: <bug-215138-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215138 Bug ID: 215138 Summary: devel/libc++ + lang/gcc: #error <atomic> is not implemented Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: needs-patch Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: gerald@FreeBSD.org Reporter: jbeich@FreeBSD.org Assignee: gerald@FreeBSD.org Flags: maintainer-feedback?(gerald@FreeBSD.org) Until OpenMP situation improves C++ ports have to resort to USES=3Dcompiler:gcc-c++11-lib. However, libc++ from ports appears to be too= old to know about GCC atomic support. $ pkg install -y gcc $ cat >a.cc #include <atomic> int main() { return 0; } $ g++49 -std=3Dc++11 -nostdinc++ -isystem /usr/local/include/c++/v1 a.cc In file included from a.cc:1:0: /usr/local/include/c++/v1/atomic:539:2: error: #error <atomic> is not implemented #error <atomic> is not implemented ^ $ find /usr/local/lib/gcc49 -name '*atomic*' /usr/local/lib/gcc49/include/c++/ext/atomicity.h /usr/local/lib/gcc49/include/c++/atomic /usr/local/lib/gcc49/include/c++/i386-portbld-freebsd11.0/bits/atomic_word.h /usr/local/lib/gcc49/include/c++/bits/atomic_lockfree_defines.h /usr/local/lib/gcc49/include/c++/bits/atomic_base.h /usr/local/lib/gcc49/libatomic.so /usr/local/lib/gcc49/libatomic.so.1.1.0 /usr/local/lib/gcc49/libatomic.a /usr/local/lib/gcc49/libatomic.so.1 /usr/local/lib/gcc49/gcc/i386-portbld-freebsd11.0/4.9.4/include/stdatomic.h https://github.com/llvm-mirror/libcxx/commit/e8b4232e3 https://github.com/llvm-mirror/libcxx/commit/00f4a49b0 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215138-13>