search for: cmake_c_compil

Hi Rafael, I looked at the code which you pushed a while ago to check for the gold linker. Code below: execute_process( COMMAND ${CMAKE_C_COMPILER} -Wl,--version OUTPUT_VARIABLE stdout ERROR_QUIET) if("${stdout}" MATCHES "GNU gold") set(LLVM_LINKER_IS_GOLD ON) endif() I was trying to build runtime libraries (compiler-rt) for ARM using “clang” which includes this code. A while ago, I saw the...

...On Wed, Jan 28, 2015 at 2:27 AM, Sumanth Gundapaneni <sgundapa at codeaurora.org <mailto:sgundapa at codeaurora.org> > wrote: Hi Rafael, I looked at the code which you pushed a while ago to check for the gold linker. Code below: execute_process( COMMAND ${CMAKE_C_COMPILER} -Wl,--version OUTPUT_VARIABLE stdout ERROR_QUIET) if("${stdout}" MATCHES "GNU gold") set(LLVM_LINKER_IS_GOLD ON) endif() I was trying to build runtime libraries (compiler-rt) for ARM using “clang” which includes this code. A while ago, I saw the...

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 problem is that native tools like llvm-config, llvm-tblgen and clang-tblgen, which must be built by the native compiler, are also created by the target compiler. What cmake / "toolchain file"...

...this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on Ubuntu, Cygwin, etc). I'm trying to recreate this with cmake so we don't get stuck on 3.8 indefinitely. Here's what I've got so far: cmake .. -DCMAKE_C_COMPILER=/usr/bin/i686-w64-mingw32-gcc \ -DCMAKE_CXX_COMPILER=/usr/bin/i686-w64-mingw32-g++ \ -DCMAKE_SYSTEM_NAME=Windows \ -DCMAKE_RC_COMPILER=/usr/bin/i686-w64-mingw32-windres # (some older versions of cmake have issues if you don't # specify an absolute path to windres) When this gets to &qu...

I'm an idiot and sent to llvm-commits instead of llvm-dev. Fixing. On 10/17/17, 5:09 PM, "llvm-commits on behalf of Shoaib Meenai via llvm-commits" <llvm-commits-bounces at lists.llvm.org on behalf of llvm-commits at lists.llvm.org> wrote: Hi all (CC beanz for cmake advice), I'm running into a cmake problem when I try to cross-compile a

Hello, I have a working GCC toolchain and wanted to use LLVM tooling instead. Following the instructions on the website I set up my build directory and have lld as an internal project under tools/. I'd like to make use of lld in stage 2 of the build and thought -DLLVM_ENABLE_LLD was the correct option to pass. However, adding this options makes the configure step fail, complaining that the

...#39;s the change I'm looking for: diff --git a/cmake/platforms/Android.cmake b/cmake/platforms/Android.cmake index 72849b1..5f732ce 100644 --- a/cmake/platforms/Android.cmake +++ b/cmake/platforms/Android.cmake @@ -11,8 +11,15 @@ # make <target> SET(CMAKE_SYSTEM_NAME Linux) + +IF(NOT CMAKE_C_COMPILER) SET(CMAKE_C_COMPILER ${CMAKE_BINARY_DIR}/../bin/clang) +ENDIF() + +IF(NOT CMAKE_CXX_COMPILER) SET(CMAKE_CXX_COMPILER ${CMAKE_BINARY_DIR}/../bin/clang++) +ENDIF() + SET(ANDROID "1" CACHE STRING "ANDROID" FORCE) SET(ANDROID_COMMON_FLAGS "-target arm-linux-androideabi...

https://bugs.freedesktop.org/show_bug.cgi?id=98852 Bug ID: 98852 Summary: Nvidia graphics card fan not running or to slow, danger of overheating Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

...---------------------------- The C compiler identification could not be found in "C:/LLVM/Build/CMakeFiles/3.18.0/CompilerIdC/a.exe" --------------------------------------- In spite of that error, here is what appears in the CMake cache: ------------------------------------ //C compiler CMAKE_C_COMPILER:FILEPATH=C:/MinGW/bin/gcc.exe //A wrapper around 'ar' adding the appropriate '--plugin' option // for the GCC compiler CMAKE_C_COMPILER_AR:FILEPATH=C:/MinGW/bin/gcc-ar.exe //A wrapper around 'ranlib' adding the appropriate '--plugin' option // for the GCC compile...

...nja CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build t ool. CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_C_COMPILER_ENV_VAR CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_C_COMPILER CMake Error: Could not find cmake module file: E:/llvm/compiler-rt-ninja/CMakeFi les/2.8.12.2/CMakeCCompiler.cmake CMake Error: Error required internal...

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

...e all different machines). > > In compiler-rt, I'd configure such a build with the following CMake variables: I'm not sure we're on the same page... Your example, and the way that lit is currently set up, assumes BUILD and HOST are the same machine. > LLVM_LIT=$BUILD/lit > CMAKE_C_COMPILER=$HOST/clang > COMPILER_RT_EMULATOR=$TARGET/qemu Let me give a concrete example: BUILD=i686-pc-linux-gnu HOST=i386-pc-win32 TARGET=arm-elf (on say, real hardware, or i686-pc-linux/bin/qemu-system-arm, or i386-pc-win32/bin/qemu-system-arm) Here I'd like to run lit on the linux machine suc...

On 9/8/14, 12:39 PM, Greg Fitzgerald wrote: > Hi Jon, > > Compiler-rt, libcxx, libcxxabi should all use the same > cross-compilation testing strategy. Compiler-rt already has a working > solution. If it is inadequate for libcxx or libcxxabi, can we start > by addressing those deficiencies? One issue to start with is that none of the libcxx/libcxxabi tests have RUN lines. All

...ault behaviour of the compiler > at build time. > > I may be wrong, though. yes I thought that was what he wanted because he said Are they used to indicate that if the C/C++ compiler for building LLVM is > clang > That combined with the standard cmake flags cmake_cxx_compiler and cmake_c_compiler should result in the host being clang and using libc++ and libc++abi I was a little thrown off by the wording of the question I think you are more correct though I misread the second part of the question where he said what he actually wanted the resulting compiler to use libc++ Sorry for the nois...

Tom Care <tcare at apple.com> writes: > This was after starting with an empty build directory. It seems to > work if I omit -DLLVM_TARGETS_TO_BUILD=X86, but a few days ago this > was working with just this target. Yep. I can replicate the problem on Linux with mkdir foo && cd foo cmake -DLLVM_TARGETS_TO_BUILD=X86 ../llvm I'll investigate a bit.

On 3 October 2014 14:42, Evgeniy Stepanov <eugenis at google.com> wrote: > this happens when x86 target is not compiled in. We really should (and > will) do something about it. > > Btw, you've asked the same question a month ago :) Sorry it has been > an issue for such a long time. No worries, I also haven't done much. But I need to get the RT bot green soon enough.

...ption:* Configure cmake with prior built clang and clang++ via gcc-4.6.3 under /usr/local/bin... /clang .../clang++ as follows: > 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...

On Wed, Aug 5, 2020 at 3:51 PM Eli Friedman <efriedma at quicinc.com> wrote: > I’m not a fan of keeping important data outside the IR in an analysis. If > we’re planning to emit it, it should be represented directly in the IR. Is > there some reason we can’t just stick the data in a global variable? > The analysis in the scenarios here is external to LLVM - ML training, for

...OFF? > 4) Set LLVM_PARALLEL_LINK_JOBS=1 (probably not needed) I'll try this next time, just to see how much of a difference it makes when I run with with -j4. > 5) Build with -w, to avoid occasional issues with warnings only > emitted by clang (probably not needed) > 6) Specified CMAKE_C_COMPILER and CMAKE_CXX_COMPILER explicitly (you > might have had the right versions in your path?) I've exported CXX and CC to clang++ and clang, which happen to be the locally build 3.9 release branch versions (non-LTO variant). > I did an nm on the .so libraries to see where __morestack was...

Hi all, CMake seems to have broken in the last few days - or is it just me? tcare:llvm-release tcare$ make -j4 -- Target triple: x86_64-apple-darwin10.5.0 -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Targeting X86 CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMARMAsmParser not found in list of llvm libraries. Call Stack (most