search for: clang_default_cxx_stdlib

...d toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt LIBCXX_CXX_ABI = libcxxabi LLVM_DEFAULT_TARGET_TRIPLE = x86_64-pc-linux-musl LIBCXXABI_TARGET_TRIPLE = x86_64-pc-linux-musl LIBUNWIND_TARGET_TRIPLE = x86_64-pc-linux-musl DEFAULT_SYSROOT = /path/to/musl GCC_INSTALL_PREFIX = /pat...

...vin 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 >> LIBCXX_HAS_GCC_S_LIB=OFF >> CLANG_DEFAULT_CXX_STDLIB=libc++ >> CLANG_DEFAULT_LINKER=lld >> CLANG_DEFAULT_RTLIB=compiler-rt >> LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >> LLVM_TARGET_ARCH=x86_64 >> LLVM_TARGETS_TO_BUILD=X86 >> >> When linking libc++.so there are a lot of undefined r...

...d toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt CLANG_DEFAULT_LINKER = lld LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl I use cmake to configure and ninja to build. It configures fine and builds, but I need libcompiler_rt.so and it is not among build targets, so it is not built and ins...

...es with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. >>> >>> I'm trying to configure with the following options: >>> CLANG_DEFAULT_CXX_STDLIB = libc++ >>> CLANG_DEFAULT_RTLIB = compiler-rt >>> CLANG_DEFAULT_LINKER = lld >>> LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >>> >>> I use cmake to configure and ninja to build. >>> >>> It configures fine and builds...

...th Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. > > I'm trying to configure with the following options: > CLANG_DEFAULT_CXX_STDLIB = libc++ > CLANG_DEFAULT_RTLIB = compiler-rt > CLANG_DEFAULT_LINKER = lld > LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl > > I use cmake to configure and ninja to build. > > It configures fine and builds, but I need libcompiler_rt.so and it is not among build tar...

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 LIBCXX_HAS_GCC_S_LIB=OFF CLANG_DEFAULT_CXX_STDLIB=libc++ CLANG_DEFAULT_LINKER=lld CLANG_DEFAULT_RTLIB=compiler-rt LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl LLVM_TARGET_ARCH=x86_64 LLVM_TARGETS_TO_BUILD=X86 When linking libc++.so there are a lot of undefined references to __cxa_allocate_exception, __cxa_begin_catch,...

...ve LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. >> >>  I'm trying to configure with the following options: >>     CLANG_DEFAULT_CXX_STDLIB = libc++ >>     CLANG_DEFAULT_RTLIB = compiler-rt >>     CLANG_DEFAULT_LINKER = lld >>     LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >> >>  I use cmake to configure and ninja to build. >> >>  It configures fine and builds, but I need libcompiler_rt.so...

...dev] Errors in configuration for LLVM with CMake GUI > After it finishes trying to configure, it says that there were errors with > the configure step and that program files may be invalid. And I also don't > know what executable to point it to for SVN. > > What should I put for CLANG_DEFAULT_CXX_STDLIB, CLANG_DEFAULT_LINKER, > CLANG_DEFAULT_RTLIB, CLANG_DEFAULT_STD_C and CLANG_DEFAULT_STD_CXX? Would > it be okay to provide the path to the MSVC include directory for the > CLANG_DEFAULT_CXX_STDLIB, or should I provide the path to the include > directory in the libcxx folder in the LLVM...

...ner Subject: Re: [llvm-dev] Errors in configuration for LLVM with CMake GUI After it finishes trying to configure, it says that there were errors with the configure step and that program files may be invalid. And I also don't know what executable to point it to for SVN. What should I put for CLANG_DEFAULT_CXX_STDLIB, CLANG_DEFAULT_LINKER, CLANG_DEFAULT_RTLIB, CLANG_DEFAULT_STD_C and CLANG_DEFAULT_STD_CXX? Would it be okay to provide the path to the MSVC include directory for the CLANG_DEFAULT_CXX_STDLIB, or should I provide the path to the include directory in the libcxx folder in the LLVM source tree? For t...

I probably need GCC for Git bash. And the one I have is MinGW's GCC, which is the one for Windows. I don't know why CMake is trying to find Linux headers. Hopefully someone who knows better what to do will weigh in here. @Jonathan Goodwin<mailto:jondgoodwin at gmail.com> , are you sure you didn't have to tell it where the header files for Windows are? If I need to specify

On Fri, Oct 28, 2016 at 9:17 AM, Renato Golin via cfe-dev <cfe-dev at lists.llvm.org> wrote: > I'm creating a bootstrap buildbot on AArch64 with LLD and I just > realised the "accepted" way to make clang call lld is to "symlink lld > -> ld". I understand that's how every Linux system "chooses" the > linker, but that makes deployment and

...add more options to the components. See for example: > > LIBCXX_CXX_ABI=libcxxabi > LIBCXX_USE_COMPILER_RT=On > LIBCXXABI_USE_LLVM_UNWINDER=On > LIBCXXABI_USE_COMPILER_RT=On > LIBCXX_HAS_GCC_S_LIB=Off > LIBUNWIND_USE_COMPILER_RT=On > > And as mentioned above > > CLANG_DEFAULT_CXX_STDLIB=libc++ > CLANG_DEFAULT_RTLIB=compiler-rt > CLANG_DEFAULT_LINKER=lld Thank you so much for your help, but when I try to build LLVM with LLVM like so: === snip === cmake \ -DLLVM_ENABLE_FFI=ON \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_RTTI=ON \ -DLLVM_TARGETS_TO_BUILD="host&quo...

Hi folks! I'm trying to get rid of any dependency on libgcc*, but without success so far. The following commands were executed on a freshliy installed and updated Ubuntu 16.04 LTS: === snip === sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed sudo mv /usr/local /usr/local.orig git clone https://github.com/llvm/llvm-project.git cd llvm-project; git

Folks, I'm creating a bootstrap buildbot on AArch64 with LLD and I just realised the "accepted" way to make clang call lld is to "symlink lld -> ld". I understand that's how every Linux system "chooses" the linker, but that makes deployment and validation quite cumbersome on GNU systems. I'd like to suggest a change in behaviour: // Some flag like

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...gpointPasses_LIB_DEPENDS:STATIC= //Build CLANG example programs by default. CLANG_BUILD_EXAMPLES:BOOL=ON //Build the Clang tools. If OFF, just generate build targets. CLANG_BUILD_TOOLS:BOOL=ON //Default C++ stdlib to use ("libstdc++" or "libc++", empty for // platform default CLANG_DEFAULT_CXX_STDLIB:STRING= //Default linker to use (linker name or absolute path, empty for // platform default) CLANG_DEFAULT_LINKER:STRING= //Default OpenMP runtime used by -fopenmp. CLANG_DEFAULT_OPENMP_RUNTIME:STRING=libomp //Default runtime library to use ("libgcc" or "compiler-rt", empty...