search for: dpython_execut

...\ > -DCMAKE_INSTALL_PREFIX:PATH=${InstallDir} \ > -DCMAKE_C_COMPILER=${GCCDir}/bin/gcc \ > -DCMAKE_C_FLAGS="-m64" \ > -DCMAKE_CXX_COMPILER=${GCCDir}/bin/g++ \ > -DCMAKE_CXX_FLAGS="-m64" \ > -DPYTHON_EXECUTABLE=${PythonDir}/bin/python \ > -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON \ > -DLLVM_LIBDIR_SUFFIX=64 \ > -DLLVM_TARGETS_TO_BUILD="X86" \ > ${LLVMSourceDir} > > I build LLVM, Clang, Clang extra tools, Compiler-RT and Polly toget...

...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

Hi Eugene, It is strange, I also do a clean build with CMake+make with r301734 and it is ok. Could you provide more details? Thanks Hongbin On Mon, May 1, 2017 at 10:58 AM, Eugene Zelenko via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, Michael! > > On Sun, Apr 30, 2017 at 2:06 PM, Michael Kruse <llvmdev at meinersbur.de> > wrote: > > 2017-04-29 0:49

...TH=${InstallDir} \ >>> -DCMAKE_C_COMPILER=${GCCDir}/bin/gcc \ >>> -DCMAKE_C_FLAGS="-m64" \ >>> -DCMAKE_CXX_COMPILER=${GCCDir}/bin/g++ \ >>> -DCMAKE_CXX_FLAGS="-m64" \ >>> -DPYTHON_EXECUTABLE=${PythonDir}/bin/python \ >>> -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON \ >>> -DLLVM_LIBDIR_SUFFIX=64 \ >>> -DLLVM_TARGETS_TO_BUILD="X86" \ >>> ${LLVMSourceDir} >>> >>> I build LLVM, Clang...

cmake -G Ninja -DLLVM_ENABLE_PROJECTS="debuginfo-tests" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DLLVM_TARGETS_TO_BUILD=X86 -Wno-dev ../llvm &> ../../cmake.log in cmake.log -- Targeting X86 CMake Error at /home/nnelson/Documents/llvm-project/debuginfo-tests/CMakeLists.txt:30 (message):   Cannot run debuginfo-tests without python 3 installed python3

..." \ > -DCMAKE_CXX_FLAGS="${CXXFLAGS} ${CPPFLAGS}" \ > -DCMAKE_INSTALL_PREFIX=/mingw64 \ > -DCMAKE_BUILD_TYPE=Release \ > -DLLVM_TARGETS_TO_BUILD="ARM;AArch64;CppBackend;X86" \ > -DLLVM_ENABLE_ASSERTIONS=OFF \ > -DLLVM_ENABLE_THREADS=0 \ > -DPYTHON_EXECUTABLE=/mingw64/bin/python2.exe \ > -DLLVM_ENABLE_FFI=ON \ > -DLLVM_ENABLE_SPHINX=ON \ > ../llvm > Is this not supported? We do have a build of libffi in mingw-w64 and it works well with other projects. On Tue, Jul 28, 2015 at 6:49 PM, Yaron Keren <yaron.keren at gmail.com>...

Ok just tried on Win 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 P...

I have already meet the problem before:) It's just because the installation of MSVC 2008 sp1. If you don't downgrade sp1, then we can using nmake system for example. %BLD%\cmake\bin\cmake.exe -DPYTHON_EXECUTABLE=%BLD%/python/python.exe -DCMAKE_INSTALL_PREFIX=%BLD%/llvm -G "NMake Makefiles" D:/svn/llv And it's must be working:) At lease on my computer is working:) -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo

...;m not cross-compiling so everything is done natively. I use the following 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_...

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

...CXX_FLAGS="${CXXFLAGS} ${CPPFLAGS}" \ >> -DCMAKE_INSTALL_PREFIX=/mingw64 \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DLLVM_TARGETS_TO_BUILD="ARM;AArch64;CppBackend;X86" \ >> -DLLVM_ENABLE_ASSERTIONS=OFF \ >> -DLLVM_ENABLE_THREADS=0 \ >> -DPYTHON_EXECUTABLE=/mingw64/bin/python2.exe \ >> -DLLVM_ENABLE_FFI=ON \ >> -DLLVM_ENABLE_SPHINX=ON \ >> ../llvm >> > > Is this not supported? > We do have a build of libffi in mingw-w64 and it works well with other > projects. > > On Tue, Jul 28, 2015 at 6:49 PM, Ya...

Hi, All, I follow the menu http://llvm.org/docs/GettingStartedVS.html , but still failed to build LLVM debug version. Here's error message: 7>C:\study\llvm\projects\compiler-rt\lib\asan\asan_win.cc(69): fatal error C1189: #error : Please build the runtime with a non-debug CRT: /MD or /MT Any idear? -- Best Regards, Amy -------------- next part -------------- An HTML attachment was

This test results in UNSUPPORTED on my system, since config.enable_ffi = "OFF". This is the result of LLVM_ENABLE_FFI which is OFF by default. Is it turned ON in your build? 2015-07-28 17:32 GMT+03:00 Martell Malone <martellmalone at gmail.com>: > Hi Yaron, > > I know you sent me some emails before about regression testing on MSYS2 > So you might have some idea about

Hey Guys, I'm working on a project in Android related to System-level Audio DSP Effects for Tuning Android Audio. I want to leverage Faust ( https://faust.grame.fr/) to allow users to program their own filters. Faust provides a libfaust implementation which includes a JIT Compiler which leverages LLVM and seems to be the best path for me to use. Unfortunately I'm having problems

Hi Yaron, I know you sent me some emails before about regression testing on MSYS2 So you might have some idea about this I am getting a regression error on check-llvm. With the llvm/trunk/test/ExecutionEngine/Interpreter/intrinsics.ll FAIL: LLVM :: ExecutionEngine/Interpreter/intrinsics.ll (7635 of 14266) > ******************** TEST 'LLVM :: >

Hi there, I was trying to build llvm on CentOS. The problem is that library on CentOS is always so old (Gcc, python). I managed to install local gcc and let cmake know. But I couldn't do so with python. I end up comment out the check in CMakeList.txt which is not good. I was wondering if anyone has experience building llvm (using cmake) using a local python? Thanks, XIaochu --------------

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

...hing. > > I discovered CMAKE_CXX_LINK_FLAGS. So I'm configuring like this: > > cmake -G "Unix Makefiles" -DCMAKE_C_COMPILER=clang > -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS="-stdlib=libc++" > -DCMAKE_CXX_LINK_FLAGS="-stdlib=libc++ -lc++abi > -DPYTHON_EXECUTABLE=/opt/python/2.7.9/bin/python2.7 > -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/opt/clang/dev > -DLLVM_APPEND_VC_REV=ON -DLLVM_ENABLE_CXX1Y=ON -DLLVM_ENABLE_ASSERTIONS=ON > -DLLVM_PARALLEL_COMPILE_JOBS=32 -DLLVM_PARALLEL_LINK_JOBS=32 > -DLLVM_BUILD_DOCS=ON -DCLANG_INCLUDE_DOCS=...

...g/llvm-config.h:/* Defined in debug builds and release builds if LLVM_FORCE_ENABLE_DUMP is what I see from a cmake options of... -DLLVM_LINK_LLVM_DYLIB:BOOL=ON -DCOMPILER_RT_ENABLE_IOS:BOOL=OFF -DLLVM_ENABLE_FFI=ON -DFFI_INCLUDE_DIR=/sw/include -DFFI_LIBRARY_DIR=/sw/lib -DLLVM_LIT_ARGS:STRING=-v -DPYTHON_EXECUTABLE:FILEPATH=/sw/bin/python2.7 -DLIBOMP_OSX_ARCHITECTURES=x86_64;i386 -DLLVM_ENABLE_ASSERTIONS:BOOL=OFF -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING= -DLLVM_TARGETS_TO_BUILD=X86;PowerPC;ARM -DCMAKE_INSTALL_PREFIX:PATH=/sw/opt/llvm-6.0 -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_C...

...if LLVM_FORCE_ENABLE_DUMP >> >> is what I see from a cmake options of... >> >> -DLLVM_LINK_LLVM_DYLIB:BOOL=ON -DCOMPILER_RT_ENABLE_IOS:BOOL=OFF >> -DLLVM_ENABLE_FFI=ON -DFFI_INCLUDE_DIR=/sw/include >> -DFFI_LIBRARY_DIR=/sw/lib -DLLVM_LIT_ARGS:STRING=-v >> -DPYTHON_EXECUTABLE:FILEPATH=/sw/bin/python2.7 >> -DLIBOMP_OSX_ARCHITECTURES=x86_64;i386 -DLLVM_ENABLE_ASSERTIONS:BOOL=OFF >> -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING= >> -DLLVM_TARGETS_TO_BUILD=X86;PowerPC;ARM -DCMAKE_INSTALL_PREFIX:PATH=/sw/opt/llvm-6.0 >> -DCMAKE...