search for: python_executable

...or some parts, but that's all. I would > be very sad for that to change. llvm-build (LLVMBuild.txt) requires python. The LLVM build will abort with message(FATAL_ERROR "Unable to find Python interpreter, required for builds and testing. Please install Python or specify the PYTHON_EXECUTABLE CMake variable.") without it. Michael

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

...CMAKE_BUILD_TYPE=Release (for most purpose) - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed onto C:\PROGRA~1\?) - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from llvm source tree - PYTHON_EXECUTABLE, if %PATH% does not contain python. - Consider to introduce ninja? Anyway, this could be integrated to "GettingStartedVS.html" ;) ...Takumi ps. feel free to visit and ask me on the irc, oftc#llvm.

...(for most purpose) > - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed > onto C:\PROGRA~1\?) > - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. > - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from > llvm source tree > - PYTHON_EXECUTABLE, if %PATH% does not contain python. > > - Consider to introduce ninja? > > Anyway, this could be integrated to "GettingStartedVS.html" ;) > > ...Takumi > > ps. feel free to visit and ask me on the irc, oftc#llvm. > -------------- next part -------------- An HTML...

...(for most purpose) > - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed > onto C:\PROGRA~1\?) > - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. > - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from > llvm source tree > - PYTHON_EXECUTABLE, if %PATH% does not contain python. > > - Consider to introduce ninja? > > Anyway, this could be integrated to "GettingStartedVS.html" ;) > > ...Takumi > > ps. feel free to visit and ask me on the irc, oftc#llvm. > -------------- next part -------------- An HTML...

...(for most purpose) > - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed > onto C:\PROGRA~1\?) > - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. > - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from > llvm source tree > - PYTHON_EXECUTABLE, if %PATH% does not contain python. > > - Consider to introduce ninja? > > Anyway, this could be integrated to "GettingStartedVS.html" ;) > > ...Takumi > > ps. feel free to visit and ask me on the irc, oftc#llvm. > -------------- next part -------------- An HTML...

...AKE_INSTALL_PREFIX (Who would be happy if clang were installed >> onto C:\PROGRA~1\?) >> - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and >> clang. >> - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from >> llvm source tree >> - PYTHON_EXECUTABLE, if %PATH% does not contain python. >> >> - Consider to introduce ninja? >> >> Anyway, this could be integrated to "GettingStartedVS.html" ;) >> >> ...Takumi >> >> ps. feel free to visit and ask me on the irc, oftc#llvm. >> > > -...

...eCheck cd ~/wk/LLVM/llvm/projects/compiler-rt/lib/tsan/go && env "CC=/usr/bin/cc " IN_TMPDIR=1 SILENT=1 ~/wk/LLVM/llvm/projects/compiler-rt/lib/tsan/go/buildgo.sh [3/4] cd ~/wk/LLVM/build_release/projects/compiler-rt/lib && env LLVM_CHECKOUT=~/wk/LLVM/llvm SILENT=1 TMPDIR= PYTHON_EXECUTABLE=/usr/bin/python2.7 COMPILER_RT=~/wk/LLVM/llvm/projects/compiler-rt ~/wk/LLVM/llvm/projects/compiler-rt/lib/sanitizer_common/scripts/check_lint.sh ninja: build stopped: subcommand failed. Even ninja -v resulted in SILENT=1 being passed to buildgo.sh, so I tried to run it manually: ~/wk/LLVM/build_...

.../lib/tsan/go && env >> "CC=/usr/bin/cc " IN_TMPDIR=1 SILENT=1 >> ~/wk/LLVM/llvm/projects/compiler-rt/lib/tsan/go/buildgo.sh >> [3/4] cd ~/wk/LLVM/build_release/projects/compiler-rt/lib && env >> LLVM_CHECKOUT=~/wk/LLVM/llvm SILENT=1 TMPDIR= >> PYTHON_EXECUTABLE=/usr/bin/python2.7 >> COMPILER_RT=~/wk/LLVM/llvm/projects/compiler-rt >> >> ~/wk/LLVM/llvm/projects/compiler-rt/lib/sanitizer_common/scripts/check_lint.sh >> ninja: build stopped: subcommand failed. >> >> Even ninja -v resulted in SILENT=1 being passed to buildgo...

...AKE_INSTALL_PREFIX (Who would be happy if clang were installed >> onto C:\PROGRA~1\?) >> - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and >> clang. >> - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from >> llvm source tree >> - PYTHON_EXECUTABLE, if %PATH% does not contain python. >> >> - Consider to introduce ninja? >> >> Anyway, this could be integrated to "GettingStartedVS.html" ;) >> >> ...Takumi >> >> ps. feel free to visit and ask me on the irc, oftc#llvm. >> > > &...

I'm trying to build llvm from svn. I ran ./configure with --enable-debug-runtime, then make -j4, before I got the following error: llvm[1]: Building llvm-config script. make[1]: Leaving directory `/home/vk/opt/llvm/tools/llvm-config' make[1]: Entering directory `/home/vk/opt/llvm/tools/llvm-config-2' llvm[1]: Constructing LLVMBuild project information. Traceback (most recent call

For those interested in the actual file, it is now attached. ---------- Forwarded message ---------- From: Mikael Lyngvig <mikael at lyngvig.org> Date: 2012/6/16 Subject: RFC: "Building with MinGW on Windows" (DOC, NEW) To: LLVMdev Mailing List <llvmdev at cs.uiuc.edu> Here's the first part of my Windows set up documentation. This one only covers the process of

On 14 December 2014 at 20:50, David Majnemer <david.majnemer at gmail.com> wrote: > Just a reminder, these bots are still not operational because of this > change. Well, there were valid objections to lowering the requirement. If we can require the host compiler to be upgraded, it is probably ok to require python to be upgraded too, no? Cheers, Rafael

I have not, I was going to look at it tonight. I tried an earlier version and got stuck trying to figure out how to invoke lit.py. Looking over ' http://llvm.org/docs/TestingGuide.html' its still clear to be how to do that. In my setup, I have an out of tree build. Could you give be an example of the command line to invoke the tests? -Nathan On Mon, Jun 14, 2010 at 1:47 PM, Michael

...> "CC=/usr/bin/cc " IN_TMPDIR=1 SILENT=1 >>>> ~/wk/LLVM/llvm/projects/compiler-rt/lib/tsan/go/buildgo.sh >>>> [3/4] cd ~/wk/LLVM/build_release/projects/compiler-rt/lib && env >>>> LLVM_CHECKOUT=~/wk/LLVM/llvm SILENT=1 TMPDIR= >>>> PYTHON_EXECUTABLE=/usr/bin/python2.7 >>>> COMPILER_RT=~/wk/LLVM/llvm/projects/compiler-rt >>>> >>>> ~/wk/LLVM/llvm/projects/compiler-rt/lib/sanitizer_common/scripts/check_lint.sh >>>> ninja: build stopped: subcommand failed. >>>> >>>> Even ninja...

On Jun 14, 2010, at 3:41 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > Michael, > > I have not made any changes since I last posted a patch. If you > would like to make the final updates, thats fine by me. I don't mind > making the changes either, I can have them done this evening as well. I'll let you do it then, along with sorting out the macros.

Here's the first part of my Windows set up documentation. This one only covers the process of setting up a normal box for building LLVM and Clang. A later document, which will follow in a few days, will cover how to set up a buildbot slave. As usual: I'm not a psychic, so if you have opinions regarding or suggestions on this document, please feel free to share them with me (on this

...(for most purpose) > - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed > onto C:\PROGRA~1\?) > - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. > - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from > llvm source tree > - PYTHON_EXECUTABLE, if %PATH% does not contain python. > > - Consider to introduce ninja? > > Anyway, this could be integrated to "GettingStartedVS.html" ;) > > ...Takumi > > ps. feel free to visit and ask me on the irc, oftc#llvm. > -------------- next part -------------- An HTML...

...stly because debugger APIs don't seem to support looking up an arbitrary type on an arbitrary line number. We've also focused entirely on Python 3 given that Python 2 expires at the end of this year. The Dexter tests mark themselves as unsupported if the python process running lit (usually PYTHON_EXECUTABLE) isn't >= 3.0. We've been targeting Python 3.6; I'm not aware of any LLVM minimum python version requirements. Roadmap -------- Non-goals: As stated, Dexter is an integration test framework, which means that it is not intended to be used to test the output of specific optimization...

Hello llvm-devs, I'm currently starting to look at implementing compiler intrinsics for the Arm MVE vector instruction set. In a similar sort of style to the existing NEON intrinsics, this is going to involve describing the set of functions needed in Tablegen, and then processing that data into a header file and some bits and pieces to compile into clang (the list of builtins, data tables