search for: gninja

...ago one of the bots that does a bootstrap started to fail (http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer) CMake Error at projects/libcxx/CMakeLists.txt:365 (message): C++11 or greater is required but the compiler does not support c++11 I can reproduce it locally with cmake -GNinja -DCMAKE_CXX_COMPILER=clang++ ~/llvm Goes away if I remove -GNinja. (!!!) Does anyone else see this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161209/97a5dc09/attachment.html>

...p started to fail > (http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer) > > CMake Error at projects/libcxx/CMakeLists.txt:365 (message): > C++11 or greater is required but the compiler does not support c++11 > > > I can reproduce it locally with > > cmake -GNinja -DCMAKE_CXX_COMPILER=clang++ ~/llvm > > > Goes away if I remove -GNinja. (!!!) > Does anyone else see this? > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinf...

...a_XXX symbols. I didn't investigate further. >>> >>> Should this have just worked out of the box? >> >> Yes, can you post your cmake invocation, I’ll investigate. > > Sorry, I should have done that initially. I copied it from the website: > > cmake -GNinja ../llvm-project/llvm -DLLVM_ENABLE_PROJECTS="clang;libcxx;compiler-rt” It builds for me right now on OSX (running `ninja check-all` right now), can you `git pull`, try again from a clean build dir, and send me the trace (including the hash you’re on and your OS / platform as well). Thanks,...

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

...(possibly as of moving libFuzzer to compiler-rt, but there have been a few other changes in the last week or so that may be related). I'm building with a fresh top-of-tree clang and setting -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which was working before: % cmake -GNinja \ -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ -DLLVM_ENABLE_WERROR=On \ -DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On \ -DCMAKE_C_COMPILER=$HOME/llvm-lkgc/bin/clang \ $HOME/code/llvm-src But when I run any of the fuzzers...

where should the file build_llvm_package.bat be placed and how should the build_llvm_package.bat be called? or is there a another way to do a two stage build of the llvm project on windows starting with using visual studio 2017 community. -------------- next part -------------- An HTML attachment was scrubbed... URL:

.... To handle everything correctly, calloc() must be > "statically" intercepted before __asan_init is called from the CRT > (hence before "dynamic" interceptors are set up). > > Can you please compare what happens in your build configuration compared to: > $ cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release > -DLLVM_TARGETS_TO_BUILD=X86 .. && ninja > instead? Do I need something special to support ninja? E:\llvm\compiler-rt-ninja>cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUIL D_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 .....

...t;> have been a few other changes in the last week or so that may be related). >> >> I'm building with a fresh top-of-tree clang and setting >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which >> was working before: >> >> % cmake -GNinja \ >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ >> -DLLVM_ENABLE_WERROR=On \ >> -DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On \ >> -DCMAKE_C_COMPILER=$HOME/llvm-lkgc/bin/clang \ >> $HOME/code/llv...

...ommand line switch does not always imply absence of a choice. I took some measurements. The machine under test is an otherwise unloaded Ryzen 2 server with 6 cores / 12 threads and fast NVME SSDs running Debian sid with gcc-10.2 as the host toolchain. $ cmake ../llvm -DCMAKE_BUILD_TYPE=Debug -GNinja \ -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_EXPORT_COMPILE_COMMANDS=ON ... $ time ninja llc ... [1199/1199] Linking CXX executable bin/llc ninja llc 6858.95s user 218.53s system 1095% cpu 10:45.78 total and then: $ git apply <<'EOF' diff --git a/llvm/C...

...; choice. >> >> I took some measurements. The machine under test is an otherwise >> unloaded Ryzen 2 server with 6 cores / 12 threads and fast NVME SSDs >> running Debian sid with gcc-10.2 as the host toolchain. >> >> $ cmake ../llvm -DCMAKE_BUILD_TYPE=Debug -GNinja \ >> -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_EXPORT_COMPILE_COMMANDS=ON >> ... >> $ time ninja llc >> ... >> [1199/1199] Linking CXX executable bin/llc >> ninja llc 6858.95s user 218.53s system 1095% cpu 10:45.78 total >> >> a...

...t is 1.13 or so). * It doesn't build (at least on my machine) due to runtime errors (the build log is really unhelpful in telling me what actually went wrong). In general the build system is kinda flawed as it seems to just manually run 'make' as a single custom build step (even with a -GNinja build). * It contains a full copy of Mark Twain's novel "The Adventures of Tom Sawyer". It gets really tiring to blacklist this file on my desktop search engine as it otherwise constantly comes up in unrelated searches for words that are by accident in this novel. * The sources of mul...

I'm trying to figure out how to get, from CMake, the architecture of the platform that I'm compiling LLVM for. If I'm building LLVM on x86, I want x86. On x64 I want x86_64. On arm arm. etc. The best I can figure out so far is that I should use LLVM_HOST_TRIPLE, and extract the first component of this. At least if my understanding is correct, I should have the following behavior:

...: 283 Unsupported Tests : 1941 Unexpected Failures: 7 The clang-tidy tests fail since end of November-December. The MachO tests fail since about the beginning of December. The Polly test fails since a few days ago. (see below for more info) I'm using the following cmake cmd-line: cmake -GNinja %ROOT%/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_LIBXML2=OFF -DCMAKE_C_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/lin...

...c() must be >>> "statically" intercepted before __asan_init is called from the CRT >>> (hence before "dynamic" interceptors are set up). >>> >>> Can you please compare what happens in your build configuration compared to: >>> $ cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release >>> -DLLVM_TARGETS_TO_BUILD=X86 .. && ninja >>> instead? >> >> Do I need something special to support ninja? > > Put it onto your PATH? > e.g. you can > $ svn export http://src.chromium.org/svn/...

Hi. Failure 1: Current clang-6.0 from http://apt.llvm.org/, current sources. $ CC=clang-6.0 CXX=clang++-6.0 cmake -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi;compiler-rt;lld;polly;openmp" -DLLVM_USE_SANITIZER="Address;Undefined" -DCMAKE_BUILD_TYPE=Release -GNinja ../llvm $ ninja [200/3921] Building Attributes.gen... FAILED: include/llvm/IR/Attributes.gen.tmp cd /build/build-test && /build/build-test/bin/llvm-tblgen -gen-attrs -I /build/llvm/include/llvm/IR -I /build/llvm/include /build/llvm/include/llvm/IR/Attributes.td -o include/llvm/IR/Attributes...

...know if that changes the way libLLVM-4.0svn.so is linked... Cheers,Jonas Am Freitag, den 06.01.2017, 13:44 +0900 schrieb Rui Ueyama: > Hi Hahnfeld, > I just compiled with LLVM_LINK_LLVM_DYLIB enabled [1] and build lld with `ninja lld`. It built fine. What am I missing? > > [1] $ cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_THREADS=On -DLLVM_ENABLE_LLD=true -DLLVM_LINK_LLVM_DYLIB=true -DLLVM_ENABLE_PROJECTS='clang;lld' ../llvm-project/llvm > > On Wed, Jan 4, 2017 at 10:31 PM, Hahnfeld, Jonas via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, &...

On 11 March 2015 at 14:38, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > I agree that it's too new to make it the minimum version. It's just a feature you'll get if CMake is new enough and will gracefully handle older CMake's. I imagine that I could add the magic CMake options to my buildbot's configuration on builders.py and locally install CMake 3.2 on them

...ab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer) >> >> CMake Error at projects/libcxx/CMakeLists.txt:365 (message): >> C++11 or greater is required but the compiler does not support c++11 >> >> >> I can reproduce it locally with >> >> cmake -GNinja -DCMAKE_CXX_COMPILER=clang++ ~/llvm >> >> >> Goes away if I remove -GNinja. (!!!) >> Does anyone else see this? >> >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http:...

...to produce `lib\LLVM.lib`. If I just build static-linked Clang/LLVM (default), it works fine. Windows bot of WebAssembly waterfall is also affected: https://github.com/WebAssembly/waterfall/commit/2051fd4cdb2b4017e66dfcd70203d40f3d0b461d Compiler: Visual Studio 2017 CMake configuration: cmake -GNinja -Bbuild -Hllvm -DCMAKE_BUILD_TYPE=Release -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_INCLUDE_TESTS=OFF -DCMAKE_INSTALL_PREFIX=d:\a\1\b -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly

Hi, Since I've migrated to a newer linux distro I can't build docs-clang-html. 1. get LLVM 2. cmake -GNinja -DLLVM_ENABLE_SPHINX=YES -DSPHINX_OUTPUT_HTML=YES -DLLVM_BUILD_DOCS=YES ~/llvm 3. ninja docs-clang-html ======================= [1/2] Generating html Sphinx documentation for clang into "/tmp/LLVM/tools/clang/docs/html" FAILED: tools/clang/docs/CMakeFiles/docs-clang-html cd /tmp/LLVM/to...