similar to: [LLVMdev] where to send test suite errors

Open bug reports, and if you could add me to the CC list that would be great. I did the Solaris port for a customer and I have a couple of diffs that I need to commit, which may fix some things for you. I'm not sure how applicable it is to Illumos, but on Solaris 10 and 11 on x86-64 they've got LLVM/Clang (self-hosting) running on top of libc++ / libcxxrt and able to build their own

illumos has done a free and clear implementation of locale support for libc, and, in fact, it was taken from FreeBSD. Have a look at: https://www.illumos.org/projects/illumos-gate/repository/show/usr/src/lib/libc/port/locale I'd love it if we could get libc++ ported to illumos. I've got two bugs already filed for issues I had with the build infrastructure that our porting system turned

Hi Bayard, (and apologies to anyone for whom this is off-topic) On 10 Apr 2012, at 19:56, Bayard Bell wrote: > illumos has done a free and clear implementation of locale support for > libc, and, in fact, it was taken from FreeBSD. Have a look at: > > https://www.illumos.org/projects/illumos-gate/repository/show/usr/src/lib/libc/port/locale I saw that, but unfortunately it's

On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s implementation), so there is no dependency of anything on libc++. Similarly, we support building libc++

On 28 Jul 2016, at 08:59, Renato Golin <renato.golin at linaro.org> wrote: > > On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s

On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: > >> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org> wrote: ... >> What are all these 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: >

On 5 Jun 2017, at 15:17, Jonathan Roelofs via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 6/5/17 5:17 AM, Dmitry Golovin via llvm-dev wrote: >> I'm trying to build LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. >> >> The configuration is the following: >> >> LIBCXX_HAS_MUSL_LIBC=ON >>

On 10/29/13 07:01 AM, Richard Smith wrote: > > [As an aside: I use libc++ for my Clang development (on Ubuntu Linux), > and it works for me (tm). This is with libstdc++ providing the ABI > pieces, rather than libc++abi or libcxxrt, though.] libc++ "works" for us as well, but it can't self host. I don't know if your "works" and my definition of works is

Hello, I wanted to try the new c++ stuff, ie clang-3.2, libc++ and libcxxrt, so I used poudriere to build a jail setup for that ( WITH_LIBCPLUSPLUS=yes in src.conf, CXXFLAGS+=-stdlib=libc++ and libsupc++.so.1 libcxxrt.so.1 in libmap.conf ), and started to build my normal set of packages ( see desktop.list ). Please note that I also have WITH_NEW_XORG=yes and WITH_KMS=yes, as well as using the

On 9 Feb 2018, at 22:30, Dimitry Andric <dimitry at andric.com> wrote: > > On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >> >> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>>> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org>

On 12/19/11 7:19 PM, Howard Hinnant wrote: > On Dec 19, 2011, at 7:14 PM, Shea Levy wrote: > >> Hello all, >> >> Is it possible, if using libc++ and compiler-rt, to have a clang with no >> runtime dependencies on any GCC components on Linux? If not, will this >> ever be possible? > We are working on a new libc++abi: http://libcxxabi.llvm.org/ which carries

On 10/3/14 10:16 AM, Dan Albert wrote: >> >> I try to build libc++ and libc++abi for host x86_64(linux) and target >> arm(linux) but fail. >> > > Failing in what way? If this isn't working out of the box, we've done > something wrong. Yeah, it would help to know more specifics about where you're getting stuck. > > jroelofs might know more... For

Hello Alexey, I just worked out the config for the FreeBSD 9.2 buildbot (follows below). One important thing about this config is that the C++11 headers 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

Hello,    I get the following error while trying to configure an llvm build on Solaris 10-SPARC: CMake Error at projects/libcxx/CMakeLists.txt:268 (message):   C++11 is required but the compiler does not support -std=c++11 However, the error is about a missing header file (llvm/Support/Solaris.h) as reported in build/CMakeFiles/CMakeError.log: Performing C++ SOURCE FILE Test

On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: > > On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> >>> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org> wrote: > ... >>> What are all these test failures? Does it seems like they have a >>>

On Mon, Oct 28, 2013 at 4:47 PM, "C. Bergström" <cbergstrom at pathscale.com>wrote: > For those driving c++11 in clang/llvm - Would it generally be acceptable > to have a "sunrise" period where the preliminary evaluation has been done > (buildbots, compiler evaluate.. etc) and the 1st actual c++11 commit hits > the repo. (30-60 days?) > I believe we

For those driving c++11 in clang/llvm - Would it generally be acceptable to have a "sunrise" period where the preliminary evaluation has been done (buildbots, compiler evaluate.. etc) and the 1st actual c++11 commit hits the repo. (30-60 days?) ------------- My concern/thoughts - When we swap out STDCXX for libc++ - We aren't able to self host clang. This could be entirely *our*

On Sun, Feb 11, 2018 at 3:31 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2018, at 22:30, Dimitry Andric <dimitry at andric.com> wrote: >> >> On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >>> >>> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org>

Hi cschen, It seems that libunwind (the one included in libcxxabi) is mandatory at the moment. Use the second build command instead: $ CROSS_COMPILING=arm ENABLE_LIBUNWIND=1 ./scripts/compile-all.sh Logan On Tue, Oct 7, 2014 at 5:32 PM, gamma_chen <gamma_chen at yahoo.com.tw> wrote: > After do "sudo apt-get update", the following are pass. > > Install the

Hi There, I am trying to build a cross-compiler for an architecture with MIPS like ISA. To begin with, I built a toolchain for MIPSr2 which uses: Clang-3.1 for preprocessing, compiling, optimizing; Binutils-2.22 for assembling and linking; Newlib-1.20.0 as the standard C library implementation. I modified the Clang Driver to use the correct binutils tools and linker scripts. Compiling Newlib with