search for: dllvm_build_test

...linaro.org>wrote: > >> Chandler, >> >> I may be doing this wrong, but I'm getting a weird error in building LLVM >> with Clang via CMake. >> >> On x86_64: >> $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm >> -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True >> -DLLVM_ENABLE_ASSERTIONS=True >> >> On ARM: >> $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release >> -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_C_FLAGS=-mcpu=cortex-a15 >> -DCMAKE_CXX_FLAGS=-mcpu=cortex-a15 -DLLVM_TARGETS_TO_BUILD=AR...

Chandler, I may be doing this wrong, but I'm getting a weird error in building LLVM with Clang via CMake. On x86_64: $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True On ARM: $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_C_FLAGS=-mcpu=cortex-a15 -DCMAKE_CXX_FLAGS=-mcpu=cortex-a15 -DLLVM_TARGETS_TO_BUILD=ARM -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=Tr...

...How do I find out which llvm libs I can't link with a dynamically loaded plugin? How can I use the EngineBuilder in my plugin with proper symbol resolution? For reproductivity: cmake -G "Sublime Text 2 - Ninja" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DLLVM_EXPORT_SYMBOLS_FOR_PLUGINS=ON -DLLVM_BUILD_TESTS=ON -DLLVM_BUILD_EXAMPLES=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" -DLLVM_TOOL_CLANG_BUILD=ON -DLLVM_TOOL_CLANG_TOOLS_EXTRA=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCLANG_BUILD_EXAMPLES=ON -DCLANG_PLUGIN_SUPPORT=ON Hope someone can help me out. Viktor -------------- next part -------...

...> mdriftmeyer at horus:~/DeveloperProjects/LLVMProject/cmake-llvm$ cmake > -DCMAKE_BUILD_TYPE=MinSizeRel > -DCMAKE_CXX_COMPILER=/usr/local/bin/clang++ > -DCMAKE_C_COMPILER=/usr/local/bin/clang -DCMAKE_CXX_FLAGS='-O2' > CMAKE_C_FLAGS='-O2' -DLLVM_BUILD_EXAMPLES=ON -DLLVM_BUILD_TESTS=ON > -DLLVM_INCLUDE_TESTS=ON > -DLLVM_TARGETS_TO_BUILD='ARM;CppBackend;PTX;Hexagon;X86' ../trunk/llvm/ > -- Target triple: x86_64-unknown-linux-gnu > -- Native target architecture is X86 > -- Threads enabled. > -- Building with -fPIC > -- Constructing LLVMBuild proje...

I'm getting this link failure when running ninja check on Linux. I'm configuring with shared libraries enabled, so I'm not sure why asan is looking for .a archives. $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=ON -DCLANG_INCLUDE_DOCS=ON -DBUILD_SHARED_LIBS=ON ../llvm $ ninja check-all FAILED: cd [..]bld/projects/compiler-rt/lib/asan/tests && [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS...

...nEngineBindings.cpp:188: undefined reference to `llvm::setFunctionAttributes(llvm::StringRef, llvm::StringRef, llvm::TargetOptions const&, llvm::Module&, bool)' collect2: error: ld returned 1 exit status This is my CMake command line: cmake -G Ninja $LLVM_SRC -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=False -DLLVM_INCLUDE_EXAMPLES=False -DLLVM_ENABLE_ASSERTIONS=True -DBUILD_SHARED_LIBS=True -DLLVM_TARGETS_TO_BUILD="ARM;X86;AArch64" -DPYTHON_EXECUTABLE=/usr/bin/python2 Static object compilation is unaffected. Any ideas? cheers, --renato

...;> >>>> I may be doing this wrong, but I'm getting a weird error in building >>>> LLVM with Clang via CMake. >>>> >>>> On x86_64: >>>> $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm >>>> -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True >>>> -DLLVM_ENABLE_ASSERTIONS=True >>>> >>>> On ARM: >>>> $ CC=clang CXX=clang++ cmake -G Ninja ../src/ >>>> -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../install >>>> -DCMAKE_C_FLAGS=-mcpu=cortex-a15 -DCMAKE_CXX_F...

...o Novillo <dnovillo at google.com> wrote: > > I'm getting this link failure when running ninja check on Linux. I'm > configuring with shared libraries enabled, so I'm not sure why asan is > looking for .a archives. > > $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=ON > -DCLANG_INCLUDE_DOCS=ON -DBUILD_SHARED_LIBS=ON ../llvm > $ ninja check-all > FAILED: cd [..]bld/projects/compiler-rt/lib/asan/tests && > [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls...

...com> > wrote: > >> >> I'm getting this link failure when running ninja check on Linux. I'm >> configuring with shared libraries enabled, so I'm not sure why asan is >> looking for .a archives. >> >> $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=ON >> -DCLANG_INCLUDE_DOCS=ON -DBUILD_SHARED_LIBS=ON ../llvm >> $ ninja check-all >> FAILED: cd [..]bld/projects/compiler-rt/lib/asan/tests && >> [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_asm_tes...

...es on an old PowerMac with OS X 10.5. After download and unpack into LLVM_SOURCE_DIR (with --strip-components=1), I configure with: cmake -DCMAKE_INSTALL_PREFIX="/opt/llvm" \ -DLLVM_TARGETS_TO_BUILD="PowerPC" \ -DLLVM_INCLUDE_TOOLS="ON" \ -DLLVM_BUILD_TESTS="ON" "$LLVM_SOURCE_DIR" It results in "llvm-config not found: specify LLVM_CONFIG_PATH". The docs at https://llvm.org/docs/CMake.html don't appear to discuss LLVM_CONFIG_PATH. I'm building out-of-tree with these two variables: LLVM_SOURCE_DIR=&q...

The configuration we’re mentioning is a 2-stage bootstrap: You need first to build without LTO your own clang, and then use it for the LTO build. — Mehid > On Sep 20, 2016, at 10:17 AM, Michael Kruse <llvmdev at meinersbur.de> wrote: > > I am the author of Polly's/ISL's platform tests and could reproduce > the problem on my system with this error message: > >

...o I find out which llvm libs I can't link with a dynamically loaded plugin? How can I use the EngineBuilder in my plugin with proper symbol resolution? For reproductivity: cmake -G "Sublime Text 2 - Ninja" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DLLVM_EXPORT_SYMBOLS_FOR_PLUGINS=ON -DLLVM_BUILD_TESTS=ON -DLLVM_BUILD_EXAMPLES=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" -DLLVM_TOOL_CLANG_BUILD=ON -DLLVM_TOOL_CLANG_TOOLS_EXTRA=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCLANG_BUILD_EXAMPLES=ON -DCLANG_PLUGIN_SUPPORT=ON Hope someone can help me out. Viktor LLVM Developers mailing...

...7 and the same problem occurs. I am building with : cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is also enabled. Also if you can forward me the output of llvm-pdbdump.exe -types llvm/test/DebugInfo/PDB/Inputs/symbolformat.pdb then I can compare the outputs. Thanks! On Tue, Jul 21, 2015 at 5:27 PM, Aaron Ballman <aaron at aaro...

...>>> >>> I'm getting this link failure when running ninja check on Linux. I'm >>> configuring with shared libraries enabled, so I'm not sure why asan is >>> looking for .a archives. >>> >>> $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=ON >>> -DCLANG_INCLUDE_DOCS=ON -DBUILD_SHARED_LIBS=ON ../llvm >>> $ ninja check-all >>> FAILED: cd [..]bld/projects/compiler-rt/lib/asan/tests && >>> [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o >>> ASAN_INST_TEST_...

...lowing cmake options : cmake -G "Unix Makefiles" .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_C_FLAGS="-march=armv7-a -mcpu=cortex-a9" -DCMAKE_C_COMPILER_TARGET=arm-linux-gnueabi -DPYTHON_EXECUTABLE=/usr/bin/python2.7 -DLLVM_ENABLE_LIBCXX=OFF -DLLVM_BUILD_TESTS=ON -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_ENABLE_RTTI=ON -DLLVM_ENABLE_FFI=ON -DLLVM_ENABLE_ASSERTIONS=True -DCOMPILER_RT_DEFAULT_TARGET_ONLY=ON -DCOMPILER_RT_BUILD_BUILTINS=ON -DCOMPILER_RT_BUILD_SANITIZERS=OFF -DCOMPILER_RT_BUILD_XRAY=OFF And I got the fol...

...MPILER=clang++ \     -DCMAKE_C_FLAGS="-fPIC" \     -DCMAKE_CXX_FLAGS="-std=c++11 -fPIC" \     -DLLVM_BUILD_LLVM_DYLIB=ON \     -DLLVM_LINK_LLVM_DYLIB=ON \     -DLLVM_INSTALL_UTILS=ON \     -DLLVM_ENABLE_RTTI=ON \     -DLLVM_ENABLE_FFI=ON \     -DLLVM_ENABLE_EH=ON \     -DLLVM_BUILD_TESTS=ON \     -DLLVM_BUILD_DOCS=OFF \     -DLLVM_ENABLE_SPHINX=OFF \     -DLLVM_ENABLE_DOXYGEN=OFF \     -DLLDB_DISABLE_LIBEDIT=1 \     -DSPHINX_WARNINGS_AS_ERRORS=OFF \     -DFFI_INCLUDE_DIR=$(pkg-config --variable=includedir libffi) \     -DFFI_LIBRARY_DIR:PATH="$(pkg-config --variable=li...

.... How do I find out which llvm libs I can't link with a dynamically loaded plugin? How can I use the EngineBuilder in my plugin with proper symbol resolution? For reproductivity: cmake -G "Sublime Text 2 - Ninja" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DLLVM_EXPORT_SYMBOLS_FOR_PLUGINS=ON -DLLVM_BUILD_TESTS=ON -DLLVM_BUILD_EXAMPLES=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" -DLLVM_TOOL_CLANG_BUILD=ON -DLLVM_TOOL_CLANG_TOOLS_EXTRA=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCLANG_BUILD_EXAMPLES=ON -DCLANG_PLUGIN_SUPPORT=ON Hope someone can help me out. Viktor ________________________________...

...-DCMAKE_BUILD_TYPE=Release \ > -DLLVM_BINUTILS_INCDIR=/usr/include \ > -DCMAKE_INSTALL_PREFIX=$PREFIX \ > -DLLVM_TARGETS_TO_BUILD="X86" \ > -DLLVM_ENABLE_BACKTRACES=OFF \ > -DLLVM_BUILD_EXAMPLES=OFF \ > -DLLVM_INCLUDE_EXAMPLES=OFF \ > -DLLVM_BUILD_TESTS=OFF \ > -DLLVM_INCLUDE_TESTS=OFF \ > -DLLVM_BUILD_DOCS=OFF \ > -DLLVM_INCLUDE_DOCS=OFF \ > -DLLVM_ENABLE_DOXYGEN=OFF \ > -DLLVM_ENABLE_SPHINX=OFF \ > -DLLDB_DISABLE_PYTHON=ON \ > -DCLANG_PLUGIN_SUPPORT=OFF \ > -DLLVM_ENABLE_LTO=Thin \ >...

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

Just to follow-up, I'm now encountering this as well. I'm doing this on Linux. It seems that when linking with the most-recently built clang, the unit tests are taking a while to complete. It's notably not using more than 1 thread, and if using `lld` I would have expected the linker to still be running in parallel. I'm doing this on a debug build, so that might help narrow it