similar to: Bootstrapping LLVM+LLD with GCC toolchain failure

I am trying to compile llvm using a toolchain file where I have specified the target system and compilers as suggested at https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html#cross-compilation-tool chain: set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR arm) set(CMAKE_C_COMPILER arm-unknown-linux-gnueabi-gcc) set(CMAKE_CXX_COMPILER arm-unknown-linux-gnueabi-g++) But the

I try to compile LLVM, clang, lld and libcxx together in one source directory following the instructions on the website. I'm running Arch Linux and already have LLVM, clang, lld and libcxx installed (prebuilt against libstdc++). Now I want a "pure" llvm toolchain. The following options were used: -DBOOTSTRAP_LLVM_ENABLE_LLD -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++

You also need -DLIBUNWIND_USE_COMPILER_RT=ON -DLIBCXXABI_USE_LLVM_UNWINDER=ON. This is because you set -DLIBCXXABI_USE_COMPILER_RT=ON so libc++abi.so is no longer being linked agains libgcc_s.so which is where the unwinder otherwise comes from. On Sun, May 6, 2018 at 4:05 AM via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I try to compile LLVM, clang, lld and libcxx together in one

I'm an idiot and sent to llvm-commits instead of llvm-dev. Fixing. On 10/17/17, 5:09 PM, "llvm-commits on behalf of Shoaib Meenai via llvm-commits" <llvm-commits-bounces at lists.llvm.org on behalf of llvm-commits at lists.llvm.org> wrote: Hi all (CC beanz for cmake advice), I'm running into a cmake problem when I try to cross-compile a

https://bugs.freedesktop.org/show_bug.cgi?id=98852 Bug ID: 98852 Summary: Nvidia graphics card fan not running or to slow, danger of overheating Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

On Tue, Sep 27, 2016 at 6:53 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > > On Sep 27, 2016, at 2:18 AM, Carsten Mattner <carstenmattner at gmail.com> > wrote: > > > >> On Mon, Sep 26, 2016 at 11:02 PM, Teresa Johnson <tejohnson at google.com> > wrote: > >> I'll either need to get a reproducer from you and/or try to repro

> Android runtime is special, we build it in a separate build tree configured with > -DCMAKE_TOOLCHAIN_FILE=$LLVM_CHECKOUT/cmake/platforms/Android.cmake This worked great, thanks! Would you mind tweaking Android.cmake so that I can override the location of the C compiler? The current version forces me to use the just-built-clang and that the new build directory be in a sibling directory.

Tom Care <tcare at apple.com> writes: > This was after starting with an empty build directory. It seems to > work if I omit -DLLVM_TARGETS_TO_BUILD=X86, but a few days ago this > was working with just this target. Yep. I can replicate the problem on Linux with mkdir foo && cd foo cmake -DLLVM_TARGETS_TO_BUILD=X86 ../llvm I'll investigate a bit.

On Thu, Oct 23, 2014 at 2:24 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: > I don't think this is the right approach. > > Currently we intentionally define malloc etc without changing the > names and (when stuff works ok) the linker just links all the mem > allocator calls with calls to our RTL. This is kind of a link-time > interception. How could that work

I can build llvm and associated tools in a 1 shot go using gcc and g++ but trying to use only gcc and bootstrap clang to build and link with libc++ and libc++abi on the second phase of the build, the compilation fails I have svn cloned LLVM CLANG CLANG_XTRA_TOOLS LLD LLDB POLLY COMPILER_RT OPENMP LIBCXX LIBCXXABI cmake command below cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=OFF

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

Hi all, CMake seems to have broken in the last few days - or is it just me? tcare:llvm-release tcare$ make -j4 -- Target triple: x86_64-apple-darwin10.5.0 -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Targeting X86 CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMARMAsmParser not found in list of llvm libraries. Call Stack (most

Hi Renato I had the impression that Michael actually wanted the latter, like GCC > has autoconf options to change the default behaviour of the compiler > at build time. > > I may be wrong, though. yes I thought that was what he wanted because he said Are they used to indicate that if the C/C++ compiler for building LLVM is > clang > That combined with the standard cmake

Okay, dropping gcc 4.4.3 makes sense. How do you feel about using clang 3.2 (and the upcoming 3.3) instead of tip-of-the-trunk clang? It looks like everything works great, but that you just need to make those UB tests 'unsupported' since they fail with "libclang_rt.ubsan was built without __int128 support". Thanks, Greg On Mon, May 27, 2013 at 12:36 AM, Alexey Samsonov

Hi folks! I'm trying to build LLVM with LLVM on Ubuntu using the commands below. Building it with the GNU stuff (cpp, gcc, g++ and binutils packages) works, but after removing it, moving LLVM to /usr/local and symlinking /usr/bin/ld to ld.lld, I'm getting the following: === snip === -- The C compiler identification is Clang 8.0.1 -- The CXX compiler identification is Clang 8.0.1 -- The

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

Hi Rafael, I looked at the code which you pushed a while ago to check for the gold linker. Code below: execute_process( COMMAND ${CMAKE_C_COMPILER} -Wl,--version OUTPUT_VARIABLE stdout ERROR_QUIET) if("${stdout}" MATCHES "GNU gold") set(LLVM_LINKER_IS_GOLD ON) endif() I was trying to build runtime libraries (compiler-rt)

[Cross-post to llvm-dev to make sure everybody relevant sees this] Hi, I'm currently trying to simplify the libc++/libc++abi/libunwind build systems and testing setup. In doing so, I am encountering issues related to "unusual" ways of building them. By unusual, I just mean "not the usual monorepo build with LLVM_ENABLE_PROJECTS". I would like to pin down what the set of

> On Aug 24, 2017, at 2:55 PM, Kostya Serebryany <kcc at google.com> wrote: > > Interesting. > This is a relatively new addition (fsanitize-coverage=pc-tables, which is now a part of -fsanitize=fuzzer). > The tests worked (did they? On Mac?) so I thought everything is ok. For tests we never compile the tested target with -O3 (and that wouldn’t be sufficient), and for