search for: dllvm_build_external_compiler_rt

...that has had a lot of development over the last two years. >>> >>> There are two supported ways in the LLVM build system to build compiler-rt with the just-built compiler. >>> >>> 1) The legacy way is for if compiler-rt is under LLVM/projects. You can specify -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On, which will configure compiler-rt using the just-built clang after clang is built. >> >> Why is this not the default? > > Two reasons. (1) It is buggy, and nobody fixed the issues because (2) the long-term plan is to not support building compiler-rt (or any other runtime libr...

...o figure out how to build compiler-rt 3.5.0 with Visual Studio 2013. In an autotools build or cmake on Linux, I believe putting the compiler-rt sources under llvm/projects is enough to build them automatically. Do I need to do anything specific to get the same with MSVC? I've tried setting -DLLVM_BUILD_EXTERNAL_COMPILER_RT either ON or OFF, but can't find any evidence of compiler-rt getting built. If I build compiler-rt separately, pointing it to an installed LLVM build with -DLLVM_CONFIG_PATH, the only thing that ends up in the install result is the sanitizer headers. Should this be working, or is it still u...

This is currently a rough area in our build system, but there are two CMake options you probably need to set. (1) -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On —> This option causes the build to use the just-built clang when building compiler-rt (2) -DCOMPILER_RT_DEFAULT_TARGET_ARCH=??? —> This is where you specify which architecture you want to build the compiler-rt archives and libraries for Hopefully in the near future we’ll have a better sto...

...leckner <rnk at google.com> wrote: > Kevin Enderby added those symbol uses in r270491. It has a cmake > feature test, and all the uses of those symbols appear bracketed in > HAVE_LIBXAR, so I don't know what went wrong for you. The trigger for this build failure is the usage of -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake option, the linkage failure for llvm-objdump disappears. > > On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in >> current...

...; > This is an area that has had a lot of development over the last two years. > > There are two supported ways in the LLVM build system to build > compiler-rt with the just-built compiler. > > 1) The legacy way is for if compiler-rt is under LLVM/projects. You > can specify -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. Why is this not the default? Thanks again, Hal > > 2) The new way, is to place compiler-rt under LLVM/runtimes. In this > path the build system will automatically build with the just-built >...

...easily build for multiple targets while you build clang. Thanks, -Chris > On May 3, 2016, at 7:24 PM, 王磊 <wanglei at ia.ac.cn> wrote: > > I finally solved my problem. Chris's suggestion helps much, but there are still a few problems to build cross platform compiler-rt. > -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On -> This is valid and required to force compiler-rt to be built by the just-built clang. > -DCOMPILER_RT_DEFAULT_TARGET_ARCH= -> This does not work, but -DCOMPILER_RT_DEFAULT_TARGET_TRIPLE works. > While using there two additional options, I still got errors. The build system successf...

...gt; Kevin Enderby added those symbol uses in r270491. It has a cmake >>> feature test, and all the uses of those symbols appear bracketed in >>> HAVE_LIBXAR, so I don't know what went wrong for you. >> >> The trigger for this build failure is the usage of >> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >> option, the linkage failure for llvm-objdump disappears. > > Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON > is the trigger of the build failure. Sorry for the noise there. Filed as https://llvm.org/bugs/show_bug.cgi?id=27855...

...com> wrote: >> Kevin Enderby added those symbol uses in r270491. It has a cmake >> feature test, and all the uses of those symbols appear bracketed in >> HAVE_LIBXAR, so I don't know what went wrong for you. > > The trigger for this build failure is the usage of > -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake > option, the linkage failure for llvm-objdump disappears. Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is the trigger of the build failure. Sorry for the noise there. > >> >> On Tue, May 24, 2016 at 8:07 AM, Jack Howarth v...

...gt; > This is an area that has had a lot of development over the last two years. > > There are two supported ways in the LLVM build system to build compiler-rt > with the just-built compiler. > > 1) The legacy way is for if compiler-rt is under LLVM/projects. You can > specify -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. > I thought the BUILD_EXTERNAL variables were for use when projects were not embedded within the llvm source tree (mostly in use by Takumi's flat buildbots that checout the top-level project without e...

...s in r270491. It has a cmake >>>>> feature test, and all the uses of those symbols appear bracketed in >>>>> HAVE_LIBXAR, so I don't know what went wrong for you. >>>> >>>> The trigger for this build failure is the usage of >>>> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >>>> option, the linkage failure for llvm-objdump disappears. >>> >>> Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON >>> is the trigger of the build failure. Sorry for the noise there. >> >> Fil...

...ed those symbol uses in r270491. It has a cmake >>>> feature test, and all the uses of those symbols appear bracketed in >>>> HAVE_LIBXAR, so I don't know what went wrong for you. >>> >>> The trigger for this build failure is the usage of >>> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >>> option, the linkage failure for llvm-objdump disappears. >> >> Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON >> is the trigger of the build failure. Sorry for the noise there. > > Filed as https://llvm.org...

On Mon, Feb 24, 2014 at 6:57 PM, Brad King <brad.king at kitware.com> wrote: > On 02/24/2014 09:44 AM, Alexey Samsonov wrote: > > ExternalProject_Add_Step(compiler-rt force-rebuild > > DEPENDERS build > [snip] > > doesn't work for Ninja. > > What version of CMake did you use for this test? Also 2.8.10? > Yes, 2.8.10.2 to be exact. > >

On Wed, Mar 8, 2017 at 2:03 PM Sterling Augustine <saugustine at google.com> wrote: > Yes, this is a aspect of the larger problem that clang bootstrap doesn't > work for a cross-compiler. The build (mostly?) assumes that host==target > during the build of clang itself, and then if you want another architecture > also, you run a second build of the target libraries, and

...gt; > This is an area that has had a lot of development over the last two years. > > There are two supported ways in the LLVM build system to build compiler-rt > with the just-built compiler. > > 1) The legacy way is for if compiler-rt is under LLVM/projects. You can > specify -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. > > > I thought the BUILD_EXTERNAL variables were for use when projects were not > embedded within the llvm source tree (mostly in use by Takumi's flat > buildbots that checout the top-leve...

...a cmake >>>>>> feature test, and all the uses of those symbols appear bracketed in >>>>>> HAVE_LIBXAR, so I don't know what went wrong for you. >>>>> >>>>> The trigger for this build failure is the usage of >>>>> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >>>>> option, the linkage failure for llvm-objdump disappears. >>>> >>>> Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON >>>> is the trigger of the build failure. Sorry for the noise there. >...

Hello, I haven't found any relevant info in the docs about this. I'm trying to build LLVM 3.7.1 on OS X but it fails in the configuration phase. Here are the relevant parts of the output: $ cmake -DCMAKE_INSTALL_PREFIX=/Volumes/HD2/jenkins/workspace/LLVMDev/label/osxbuild/miniconda/envs/_build -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=host -DLLVM_INCLUDE_TESTS=OFF

...passes our test suite with the Ninja generator. > > Please see if you can reproduce this with CMake 'master' from > Git: > Yep, I can reproduce it with latest CMake and ninja: $ cmake --version cmake version 3.0.20140225-gcd8c $ ninja --version 1.4.0.git I configure LLVM with -DLLVM_BUILD_EXTERNAL_COMPILER_RT=ON (with applied patches http://llvm-reviews.chandlerc.com/D2868 and http://llvm-reviews.chandlerc.com/D2874) Then I run $ ninja compiler-rt twice. The first run builds the libraries, the second shows only: "ninja: no work to do." message. > > git clone git://cmake.org/cmake.git...

Submitted r204593. On Sun, Mar 23, 2014 at 10:03 PM, Alexey Samsonov <samsonov at google.com>wrote: > Hi Dmitri, > > On Sat, Mar 22, 2014 at 11:50 PM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > >> Hello, >> >> It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS >> into account. This is because clang_compile and

Hi. I'm trying to use Clang/LLVM as a cross-compiling toolchain. In previous version of LLVM with the old configure/Makefile building system, I'm able to build Clang/LLVM for target architecture with the host GCC firstly and then use the generated cross compiler to compile the compiler-rt project, and, consequently, I can get a cross compiler as well as the compiler-rt library. However,

...;>>>> feature test, and all the uses of those symbols appear bracketed in >>>>>>> HAVE_LIBXAR, so I don't know what went wrong for you. >>>>>> >>>>>> The trigger for this build failure is the usage of >>>>>> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >>>>>> option, the linkage failure for llvm-objdump disappears. >>>>> >>>>> Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON >>>>> is the trigger of the build failure. Sorry for the no...