search for: llvm_enable_libcxx

Also please note that there is a description of each option in the CMakeLists.txt :) llvm/trunk/CMakeLists.txt option(LLVM_ENABLE_MODULES "Compile with C++ modules enabled." OFF) option(LLVM_ENABLE_CXX1Y "Compile with C++1y enabled." OFF) option(LLVM_ENABLE_LIBCXX "Use libc++ if available." OFF) option(LLVM_ENABLE_LIBCXXABI "Use libc++abi when using libc++." OFF) option(LLVM_ENABLE_PEDANTIC "Compile with pedantic enabled." ON) option(LLVM_ENABLE_WERROR "Fail and stop if a warning is triggered." OFF) Kind Regards Mart...

Hi Michael, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and > LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler > for building LLVM is clang, and if this clang has support for libc++ with > libc++Abi, that both lib++ and libc++abi should be used (instead of linking > to the default, which at least on Linux is libstd...

Hi, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used (instead of linking to the default, which at least on Linux is libstdc++)? If not, what i...

> > That's how I read it. :) :) Adding a little to the topic what criteria would we need to make a target use compiler-rt and libc++ as the default in the clang driver. I have successfully built a standalone clang toolchain with mingw-w64 without using gcc or binutils. Currently I locally patch this to be the default. On Tue, Jul 28, 2015 at 2:33 PM, Renato Golin <renato.golin at

Wouldn’t it it be possible to add a flag like the one used in the OpenMP subproject? There they default to linking to the non-functional libgomp (as far as I understand it), and if people want to use the actual libomp runtime, they have to specify -fopenmp=libomp when compiling/linking a program. At the same time, it is possible to use the libomp runtime library by default by specifying

On 28 July 2015 at 12:10, Schlottke-Lakemper, Michael <m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used (instead of linking to the default, which at least on Linux is libstdc++)? If not, what i...

On 28 July 2015 at 14:44, Martell Malone <martellmalone at gmail.com> wrote: > Adding a little to the topic what criteria would we need to make a target > use compiler-rt and libc++ as the default in the clang driver. > I have successfully built a standalone clang toolchain with mingw-w64 > without using gcc or binutils. There was another discussion with David Chisnall, where he

...is. Kind Regards Martell On Tue, Jul 28, 2015 at 1:06 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 28 July 2015 at 12:10, Schlottke-Lakemper, Michael > <m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > > I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX > and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ > compiler for building LLVM is clang, and if this clang has support for > libc++ with libc++Abi, that both lib++ and libc++abi should be used > (instead of linking to the default, which at least on Linux is libstd...

llvm/cmake/modules/HandleLLVMStdlib.cmake specifies "-stdlib=libc++" for CMAKE_CXX_FLAGS when LLVM_ENABLE_LIBCXX and CXX_SUPPORTS_STDLIB. From what I can see this is a flag intended for the linker and not the compiler. I'd like to submit a change to delete CMAKE_CXX_FLAGS from this append() but I wanted to check in with the list to see if that makes sense or if there are other contexts for which &quo...

...LIBUNWIND_TARGET_TRIPLE = x86_64-pc-linux-musl DEFAULT_SYSROOT = /path/to/musl GCC_INSTALL_PREFIX = /path/to/gcc-stub LLVM_TARGETS_TO_BUILD = X86 LIBCXXABI_USE_COMPILER_RT = ON LIBCXXABI_USE_LLVM_UNWINDER = ON LIBCXX_HAS_MUSL_LIBC = ON LIBCXX_USE_COMPILER_RT = ON LLVM_ENABLE_LIBCXX = ON LLVM_ENABLE_LLD = ON When I try to configure, I get the following error messages: CMake Warning at cmake/modules/HandleLLVMStdlib.cmake:24 (message): Can't specify libc++ with '-stdlib=' Call Stack (most recent call first): cmake/config-ix.cmake:15 (include) CMakeL...

...guess I'll postpone the rebuild until this can be resolved/explained. Also because ideally I want to do it that way, and it's a goal for a future default build config of llvm as discussed recently here, I'd prefer to build and then use the in-tree libc++. But it doesn't seem like -DLLVM_ENABLE_LIBCXX has that effect. Shouldn't it or if not why can't it? I would certainly welcome and find natural that the in-tree libc++ is used when LLVM_ENABLE_LIBCXX=ON. The need for a pre-built and installed libc++ is less practical.

.... These versions of the library have an issue, which > causes occasional lldb crashes. See > <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59656> for details. > Possible > courses of action are: > > - use libstdc++ version 4.9 or newer > > - use libc++ (via LLVM_ENABLE_LIBCXX) > > - enable exceptions (via LLVM_ENABLE_EH) > > - ignore this warning and accept occasional instability > Call Stack (most recent call first): > tools/lldb/CMakeLists.txt:4 (include) > --- > > libstdc++ is 6.2.1 so the CMake check seems wrong. > Or maybe it is...

...than 4.9 without exceptions enabled. These versions of the library have an issue, which causes occasional lldb crashes. See <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59656> for details. Possible courses of action are: - use libstdc++ version 4.9 or newer - use libc++ (via LLVM_ENABLE_LIBCXX) - enable exceptions (via LLVM_ENABLE_EH) - ignore this warning and accept occasional instability Call Stack (most recent call first): tools/lldb/CMakeLists.txt:4 (include) --- libstdc++ is 6.2.1 so the CMake check seems wrong. This prompted me to use -libstd=libc++ and -DLLVM_ENABLE_LIBC...

...--------------------------------------------- >> >> I am using GCC 4.8.5 to build on a x86_64 machine with RedHat OS. >> >> Any idea why? > > What arguments are you passing to CMake and which version of LLVM are > you > trying to build? That's probably -DLLVM_ENABLE_LIBCXX=ON and the warning tells you the reason: -stdlib= is only supported if compiling with Clang, you can't specify it with GCC. Cheers, Jonas

Thanks, that's the reason. So to clarify, I should use -DLLVM_ENABLE_LIBCXX=ON only if I am building clang with clang? I got confused, I thought it was for building libc++, but having that under projects seems to be enough. Thanks. Simone -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachment...

...il > this > can be resolved/explained. > > Also because ideally I want to do it that way, and it's a goal for a > future default > build config of llvm as discussed recently here, I'd prefer to build > and then use > the in-tree libc++. But it doesn't seem like -DLLVM_ENABLE_LIBCXX has that > effect. Shouldn't it or if not why can't it? I would certainly welcome > and find natural > that the in-tree libc++ is used when LLVM_ENABLE_LIBCXX=ON. The need for > a pre-built and installed libc++ is less practical. > I'm really not sure, and I don't bu...

On Tue, Dec 20, 2016 at 11:05 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Dec 20, 2016 at 5:05 PM, Teresa Johnson <tejohnson at google.com> > wrote: > > Hi Carsten, > > > > A few responses below, but first, can you get the link command for > > lldb.so.3.9.1? Last time it was the lldb.so build that was using > > ld.bfd with the

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

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: