similar to: Error in Windows build from release_40 branch

Hans, Am 06.03.2017 um 23:25 schrieb Hans Wennborg: > The mailing list thread you linked to talkes about > "multi-configuration generators", such as MSBuild. Have you tried > building with ninja (https://ninja-build.org/) instead? I now tried the ninja build, and that was successful, so I have a workaround. I still would like to know whether I made a mistake with the

On Wed, Mar 8, 2017 at 10:34 AM, Stephan Mühlstrasser <stephan.muehlstrasser at web.de> wrote: > Hans, > > Am 06.03.2017 um 23:25 schrieb Hans Wennborg: >> >> The mailing list thread you linked to talkes about >> "multi-configuration generators", such as MSBuild. Have you tried >> building with ninja (https://ninja-build.org/) instead? > >

> I don't think you made a mistake, I suppose something in the cmake > config is broken. Hi Hans, I can still see the MSVS install error as below with latest LLVM code. Is there any word around can let me install the LLVM through MSVS successfully? CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:37 (file): file INSTALL cannot find

Hi, I'm playing around with LLVM and stumbled upon this issue while while performing "make install". The build itself was successful. I'm using the latest git version. #make install -- Installing: /home/alesko/llvm-install/bin/llvm-mc -- Installing: /home/alesko/llvm-install/bin/sancov -- Installing: /home/alesko/llvm-install/bin/opt -- Installing:

Hi, All I have tried to compile and install LLVM on windows 8 using Visual Studio Express 2013 for Windows Desktop. The compiling is fine. However, the installing gives the following errors: 62> CMake Error at projects/compiler-rt/lib/asan/cmake_install.cmake:34 (FILE): 62> file INSTALL cannot find 62>

> On Dec 9, 2015, at 1:56 PM, Chris Bieneman via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Not sure, but my guess is that the ocaml documents targets aren’t being included in the ALL target, which is resulting in them not being built before the install action. I think you're right. Running "make ocaml_doc" then rerunning "make install" completed the

Hi All, I am first time trying build CLANG+LLVM using cmake+ninja build system. I updated all my CLANG+LLVM sources to current trunk, and I successfully built it using classic *make* build system. But, trying to build the same with cmake+ninja build system resulting in following build failures for compiler-rt sources. Am I missing something basics here? ==================== cmake command used:

I'm seeing this too. CC'ing the author ubsan stuff. Richard, I know you were OK with only supporting Clang-bootstraps, but I don't think that's terribly viable here. We should be able to build ubsan's runtime with standards conforming code unless there is some fairly extreme reason not to... On Fri, Oct 12, 2012 at 7:19 AM, Mahesha HS <mahesha.llvm at gmail.com> wrote:

I use latest cmake+ninja which are built from latest sources. ================================= > cmake --version cmake version 2.8.9.20121011-g2876 ================================= -- mahesha On Fri, Oct 12, 2012 at 7:35 PM, Mahesha HS <mahesha.llvm at gmail.com> wrote: > Hi All, > > I am first time trying build CLANG+LLVM using cmake+ninja build > system. I updated all

Hi dear list, I tried to build llvm+clang on an OpenSuse BuildServer for ARM. The build was carried out with CMake 2.8.11. In the installation step I got the following error: > [26815s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/llvm-3.4.99-336.1.arm/usr/lib/libLLVMSupport.so > [26815s] CMake Error at lib/Support/cmake_install.cmake:45 (FILE): > [26815s] file RPATH_CHANGE could

On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com> wrote: > I'm seeing this too. CC'ing the author ubsan stuff. > > Richard, I know you were OK with only supporting Clang-bootstraps, but I > don't think that's terribly viable here. Just out of curiosity - why isn't that viable? I'd sort of hope to treat optional sanitizer runtimes

On Sat, Oct 13, 2012 at 1:09 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com> > wrote: > > I'm seeing this too. CC'ing the author ubsan stuff. > > > > Richard, I know you were OK with only supporting Clang-bootstraps, but I > > don't think that's terribly viable

On Oct 25, 2011, at 6:09 AM, Marcello Maggioni wrote: > Hi, I'm trying to compile the latest clang/llvm SVN versions and I get > this error on multiple systems : Linking, not compiling, but still. I am getting a similar error when building this morning. > Undefined symbols for architecture x86_64: > "clang::Sema::checkPseudoObjectRValue(clang::Expr*)", referenced

I'm trying to figure out how to get, from CMake, the architecture of the platform that I'm compiling LLVM for. If I'm building LLVM on x86, I want x86. On x64 I want x86_64. On arm arm. etc. The best I can figure out so far is that I should use LLVM_HOST_TRIPLE, and extract the first component of this. At least if my understanding is correct, I should have the following behavior:

On 11 July 2015 at 13:14, Caldarale, Charles R <Chuck.Caldarale at unisys.com> wrote: >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] >> On Behalf Of Dibyendu Majumdar >> Subject: [LLVMdev] JIT compilation 2-3 times slower in latest LLVM snapshot > >> I updated my clone of the LLVM github mirror today and I am finding >> that

Hi, I'm trying to compile the latest clang/llvm SVN versions and I get this error on multiple systems : (Compiling with gcc): llvm[4]: Compiling cc1_main.cpp for Debug+Asserts build llvm[4]: Compiling cc1as_main.cpp for Debug+Asserts build llvm[4]: Compiling driver.cpp for Debug+Asserts build llvm[4]: Linking Debug+Asserts executable clang

Hello, I downloaded and built llvm-7.0.1 as per the instructions on the website docs. It seems that I can run many of the tools in build/bin (eg llvm-diff or count etc) with the exception of opt where I get "-bash: ./opt.exe: cannot execute binary file: Exec format error". I tried rebuilding just opt but still no luck. An ideas? This is frustrating because opt is the tool I am most

We try to change cmake's behaviour so that it uses $ORIGIN in the rpath, making the binaries relocatable. That might be falling in here for some reason. Sent from my iPhone > On Feb 12, 2014, at 11:07, Brad King <brad.king at kitware.com> wrote: > >> On 02/12/2014 08:08 AM, Mathias Bauer wrote: >> Hi dear list, >> >> I tried to build llvm+clang on an

On Fri, Sep 16, 2016 at 10:18 PM, Teresa Johnson <tejohnson at google.com> wrote: > > Cc'ing llvm-dev again in case someone knows what is going on. > > That error is coming from a polly configure script, which I don't > have cloned into my own tree. Not sure why polly would behave > differently when configuring for ThinLTO. Does polly configure ok > when

Hallo all, I was trying to Build LLVM with the cmake option LLVM_ENABLE_MODULES just out of curiosity. I used the RELEASE_400/final tag. It didn't work as I almost expected. So I'm wondering if the modulemaps aren't maintained anymore? If they aren't maintained anymore, why aren't they removed and that cmake option also removed?