search for: dcmake_c_compiler

Hi, Currently, I can build lld/llvm on Fedora 17 but fail to build it on iMac. The commands I use as follows. Anyone can help me? Or is there the lld mail list I can post the question? Linux/Fedora can be built by the following command cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_FLAGS=-std=c++11 -DCMAKE_BUILD_TYPE=Debug -G "Unix Makefiles" ../src/ make iMac cannot be built by the following command (fail on Xcode compile) cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_FLAGS=-std=c++0x -DCMAKE_BUILD_TYPE=Debug -G "Xc...

...github.com/NuxiNL/cloudlibc/wiki/Building-runtime-libraries#user-content-compiler-rt > > -DCMAKE_CROSSCOMPILING=True > > As you can see, I'm using CMake. Works pretty well so far. Hopefully > something like this will work for you as well? > I tried "cmake ../compiler-rt -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DLLVM_NATIVE_ARCH=ARM -DLLVM_TARGETS_TO_BUILD=ARM -DTARGET_TRIPLE=armv-none-linux-gnueabi -DCMAKE_CROSSCOMPILING=True". It will still build X86_64 version. I also tried "cmake ../compiler-rt -DCMAKE_C_COMPILER=/usr/local/arm-2009q3/bin/arm-none-linux...

...Hi, > > Currently, I can build lld/llvm on Fedora 17 but fail to build it on iMac. The commands I use as follows. Anyone can help me? Or is there the lld mail list I can post the question? > > Linux/Fedora can be built by the following command > cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_FLAGS=-std=c++11 -DCMAKE_BUILD_TYPE=Debug -G "Unix Makefiles" ../src/ > make > > iMac cannot be built by the following command (fail on Xcode compile) > cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_FLAGS=-std=c++0x -DCMAKE_BUILD_TY...

...ler-rt on version 9.0.0-rc3 * Built an instrumented clang with the following config: cmake -G Ninja ../llvm \ -DLLVM_ENABLE_PROJECTS='clang;compiler-rt' \ -DLLVM_TARGETS_TO_BUILD=X86 \ -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ -DCMAKE_CXX_COMPILER=/path/to/release_build/bin/clang++ \ -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ -DLLVM_CCACHE_BUILD=ON \ -DLLVM_BUILD_INSTRUMENTED=IR \ -DLLVM_BUILD_RUNTIME=No \ -DLLVM_ENABLE_ZLIB=1 \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_LTO=Thin \ -DCMAKE_RANLIB=/path/to/release_bui...

...lang with the following config: >> cmake -G Ninja ../llvm \ >> -DLLVM_ENABLE_PROJECTS='clang;compiler-rt' \ >> -DLLVM_TARGETS_TO_BUILD=X86 \ >> -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ >> -DCMAKE_CXX_COMPILER=/path/to/release_build/bin/clang++ \ >> -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ >> -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ >> -DLLVM_CCACHE_BUILD=ON \ >> -DLLVM_BUILD_INSTRUMENTED=IR \ >> -DLLVM_BUILD_RUNTIME=No \ >> -DLLVM_ENABLE_ZLIB=1 \ >> -DCMAKE_BUILD_TYPE=Release \ >>...

On 04/12/2019 06:31 PM, Tom Stellard via llvm-dev wrote: > On 04/12/2019 04:28 PM, AiChi via llvm-dev wrote: >> Hi, >> >> I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. >> >> Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++

...ToT for all of them, compiled and installed using cake). I had to add -std=c++0x to the compilation flags and -lc++abi to the linker flags, for the libcxx dir. Put lld in llvm/projects/lld [dev/llvm-build]% cmake -DLLVM_TARGETS_TO_BUILD="ARM;PowerPC;CellSPU;X86" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ ../llvm [dev/llvm-build]% make ... The error I get when I'm trying to compile is http://pastie.org/3841810 If I symlink the updated libcxx headers into lld/tools/lld-core, the file compiles cleanly (but fails linking becausee I'm not tweaking the linker...

...-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, it looks like the sanitizer coverage hasn't been set up correctly: % ./bin/llvm-as-fuzzer 2017-08-24 11:14:33 INFO...

...problem creating LLVMHello. I used this CMake file #!/bin/sh # clangcmake.sh cmake -G "Eclipse CDT4 - Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_ECLIPSE_VERSION=4.5 -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang ../llvm then I ran make LLVMHello and the build failed on an error about LLVMHello.export The problem turned out to be that the parent directory path had a space in one of the folder names. I removed the space and now LLVMHello builds properly. Hope you find this useful. Keith Smith

...pilers. gcc 5.2 with -std=c++11 This works, although there are still some warnings. gcc 6.4 and gcc 7.1 fail with errors such as this in building libcxxabi as follows: Command: /opt/cmake/bin/cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/home/fletcher/LLVM/llvm-5.0.rc2/local_71 -DCMAKE_C_COMPILER=/opt/gcc-7.1/bin/gcc CMAKE_CXX_COMPILER=/opt/gcc-7.1/bin/g++ -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_TARGETS_TO_BUILD="host" -DCMAKE_CXX_FLAGS="-std=c++11 -I/opt/gcc-7.1/include/c++/7.1.0" -DCMAKE_EXE_LINKER_FLAGS="-Xlinker -R/opt/gcc-7.1/lib64 -L/opt/g...

1) Build clang with GCC-4.9.2, when compling other application s with clang/clang++, the default linker is ld, can I replace it with other linker tool， if we can, how to do it? I.E. can we use collect2 instead? 2) how to specify the path, if we do not use the default vertion GCC? Best Regards! Eric Lew -------------- next part -------------- An HTML attachment was scrubbed... URL:

..., 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 &quot...

...AGE=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, it looks like the sanitizer coverage >> hasn't been set up correctly: >> >> % ./bin/llvm-as-fuzzer...

...and it >> is ok. Could you provide more details? >> >> Thanks >> Hongbin > > My CMake parameters: > > ${CMake} \ > -DCMAKE_BUILD_TYPE="Release" \ > -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...

...hared libraries, hence we went with it. I am testing with > -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON atm, and will let > you know if any problem arises. I am trying to enable this on openSUSE but it seems to break standalone lldb (note that we don't ship static libs): cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DLLVM_BUILD_LLVM_DYLI B=ON -DLLVM_LINK_LLVM_DYLIB=ON -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=RelWithDebInfo -DLLVM_LIBDIR_SUFFIX=64 -DLLDB_PA TH_TO_LLVM_BUILD=/usr -DLLDB_PATH_TO_CLANG_BUILD=/usr -DLLVM_RUNTIME_OUTPUT_INTDI...

...xx together in one source directory following the instructions on the website. I'm running Arch Linux and already have LLVM, clang, lld and libcxx installed (prebuilt against libstdc++). Now I want a "pure" llvm toolchain. The following options were used: -DBOOTSTRAP_LLVM_ENABLE_LLD -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_LINKER=lld -DCMAKE_LINK_EXECUTABLE="/usr/bin/ld.lld" -DCMAKE_AR="/usr/bin/llvm-ar" -DCMAKE_AS="/usr/bin/llvm-as" -DCLANG_DEFAULT_LINKER=lld -DCLANG_DEFAULT_RTLIB=compiler-rt -DCLANG_ENABLE_BOOTSTRAP=ON -DLIBCXX_USE_COMPILER_RT...

...mption:* 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 &...

...help with respect to cross compiling for ARM. While trying to cross compile for the ARM target, I am hitting some errors. I need some help in this. I use the following command to cross compile for ARM Cortex A72 (ARM v8-a), 64 bit architecture: *cmake -v CC='clang' CXX='clang++' -DCMAKE_C_COMPILER=../build_directory_llvm/bin/clang -DCMAKE_CXX_COMPILER=../build_directory_llvm/bin/clang++ -DLLVM_TABLEGEN=../build_llvm_directory/bin/llvm-tblgen -DCLANG_TABLEGEN=../build_llvm_directory/bin/clang-tblgen -DCROSSCOMPILING=True -DCMAKE_INSTALL_PREFIX=../tmp_two -DLLVM_DEFAULT_TARGET_TRIPLE=aarch64-l...

...sts 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/link.EXE" -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" -DLLVM_ENABLE_PDB=ON -DLLVM_POLLY_LINK...

I downloaded a binary build of release candidate 2, and it was simply a bare directory tree with no README files or other directions. Does one simply plop this in /usr/local or is there more to it? (I'm on OS X.) -- Perry E. Metzger perry at piermont.com