search for: cxxrt

...are set up at the /usr/include/c++/v1 directory--it's where clang expects them to be on FreeBSD, so no need for the "-I" options in the CMAKE_CXX_FLAGS variable. Unfortunately, clang (both v3.3 used to be the default compiler on FreeBSD 9.2 and recent revisions) do not add the libcxxrt run-time lib to ld options what means we have to ask cmake to add it for us (see the cmake invocation at the end of the config list). This approach let us build and run the common sanitizers tests with no unexpected failures. The only issue is that the HAVE_UNIT64_T & Co. tests fail to link...

...hese test failures? Does it seems like they have a >> common root cause and do we have a bug for it? ... > The Clang Tools and Extra Tools Unit tests all appear to crash with: > > exception_ptr not yet implemented This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am going to try the followin...

...t;>> common root cause and do we have a bug for it? >> ... >>> The Clang Tools and Extra Tools Unit tests all appear to crash with: >>> >>> exception_ptr not yet implemented >> >> This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) >> >> In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am going t...

...ems like they have a >>> common root cause and do we have a bug for it? > ... >> The Clang Tools and Extra Tools Unit tests all appear to crash with: >> >> exception_ptr not yet implemented > > This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) > > In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am going to try th...

...cause and do we have a bug for it? >>> ... >>>> The Clang Tools and Extra Tools Unit tests all appear to crash with: >>>> >>>> exception_ptr not yet implemented >>> >>> This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) >>> >>> In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am...

...bug for it? >>>> ... >>>>> The Clang Tools and Extra Tools Unit tests all appear to crash with: >>>>> >>>>> exception_ptr not yet implemented >>>> >>>> This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) >>>> >>>> In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD...

On Tue, Apr 1, 2014 at 1:23 PM, Ivan A. Kosarev <ivan at ivan-labs.com> wrote: > Hi Alexey, > > > On 03/31/2014 09:58 PM, Alexey Samsonov wrote: > > On FreeBSD 9.2 I add a couple custom options to CMAKE_CXX_FLAGS in order > to let clang know which header set it should use, like that: > >> >>> CC=clang CXX=clang++ cmake \ >>>

> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >>> >>> There's been a lot of merges since rc1, and hopefully the tests are in

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>