similar to: llvm build failed on Fedora 24

Displaying 20 results from an estimated 300 matches similar to: "llvm build failed on Fedora 24"

2011 Oct 24
1
[LLVMdev] build warnings
On Sun, Oct 23, 2011 at 10:34 PM, James Molloy wrote: > Hi, > > I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. > $ make happiness ... Updated to revision 142790. ... make[4]: Entering directory `/home/ecsardu/LLVM/build-tcclab1/tools/clang/tools/libclang' llvm[4]: Compiling
2011 Oct 23
0
[LLVMdev] build warnings
Hi, I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. Cheers, James ________________________________________ From: Csaba Raduly [rcsaba at gmail.com] Sent: 23 October 2011 18:44 To: James Molloy Cc: Paul Berube; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] build warnings On Sat, Oct 22,
2011 Oct 23
5
[LLVMdev] build warnings
On Sat, Oct 22, 2011 at 12:24 AM, James Molloy wrote: > Hi Paul, > > That should be easy enough, because the LLVM build has no warnings in it! > > Some of us build with -Werror, and even with those of us that don't warnings are not tolerated. You're already seeing all the warnings that are coming out of the build :) So, all the "variable might be used
2018 Sep 19
4
CMake build of LLVM/clang with -DCMAKE_BUILD_TYPE=Release does not create release versions?
>because with that generator the CMAKE_BUILD_TYPE variable is ignored >because it is a "multi-configuration target". thanks for the link, is that a bug in the CMake configuration (or better not getting any warning) or is there just documentation missing? so i can use --config Debug or --config Release and get the correct results - i hope that works the build takes hours
2018 Sep 19
2
CMake build of LLVM/clang with -DCMAKE_BUILD_TYPE=Release does not create release versions?
my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) directory structure test   llvm <-- git clone https://github.com/llvm-mirror/llvm     tools       clang <-- git clone https://github.com/llvm-mirror/clang   llvm_build Debug build: clean build, llvm_build is deleted before llvm_build> cmake
2018 Sep 19
2
CMake build of LLVM/clang with -DCMAKE_BUILD_TYPE=Release does not create release versions?
>are you setting the optimized tablegen option? LLVM_OPTIMIZED_TABLEGEN is not active - i will try that >In addition, make sure you have plenty of memory i've got only Intel Core 2 Quad CPU Q8300/2.50Ghz and 8GB RAM for testing not much cpu power AND memory Am 19.09.2018 um 11:31 schrieb James Henderson: > Regarding the Debug build taking hours, are you setting the optimized
2010 Mar 06
2
[LLVMdev] Cygwin patches for 2.7
On 6 March 2010 10:47, Eric Christopher <echristo at apple.com> wrote: > > On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: > > > > > clang fails with a dynamic linking problem. > > What's the problem? and if you would please file a bug that would be > awesome :) > > thanks! > > Eric, Neither Cygwin nor MinGW support Dynamic Linking. I am getting
2017 Jun 02
2
Question regarding to learn LLVM
Hi, I have basic knowledge about LLVM. I want to make expertise in it and also start contributing. So, How do I start? Where do I start? What basic fundamental knowledge is required? Any study material(books, link). Thanks, Amit G
2017 Aug 08
2
Safety of changing values of variables by editing CMakeCache.txt Vs supplying them through the command line
Hello, I'm working on a project involving LLVM and keep shifting between the Debug and Release build by assigning different values to CMAKE_BUILD_TYPE in <llvm_build>/CMakeCache.txt and then building it. I wanted to know if this was a safe alternative to re-configuring the build after removing <llvm_build>/CMakeFiles/ and <llvm_build>/CMakeCache.txt. Thanks, Sanjay
2010 Mar 06
1
[LLVMdev] Cygwin patches for 2.7
On 5 March 2010 22:09, Aaron Gray <aaronngray.lists at googlemail.com> wrote: > Thanks Chris. Built LLVM okay from SVN and am running 'make check' and > building LLVM-GCC, also will check whether clang builds on Cygwin too. > LLVM-GGC builds and installs okay using gcc-4.2.4 minimum. 'make check' runs okay too. clang fails with a dynamic linking problem. Aaron
2010 Mar 06
0
[LLVMdev] Cygwin patches for 2.7
On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: > > clang fails with a dynamic linking problem. What's the problem? and if you would please file a bug that would be awesome :) thanks! -eric
2010 Mar 06
2
[LLVMdev] Cygwin patches for 2.7
On Mar 6, 2010, at 3:49 AM, Aaron Gray wrote: > > I am hoping I can just not build the indexer and will see if I can get a patch together first for 2.7 before submitting a bug report if I have to. > > Okay here's a patch to no build the CIndexer on Cygwin and MinGW :- > > Index: tools/Makefile > =================================================================== >
2016 Jun 23
4
[cfe-dev] clang++ build from source is not able to find C++ headers
Hi Vivek, you can also include these lines below to your ~/.bash_profile: LLVM_BUILD="/Developer/llvm/build" # Path to your build directory alias new-clang="$LLVM_BUILD/bin/clang -Wno-expansion-to-defined -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include" alias new-clang++="$LLVM_BUILD/bin/clang++
2013 Jul 14
5
[LLVMdev] Analysis of polly-detect overhead in oggenc
At 2013-07-14 13:20:42,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/13/2013 09:18 PM, Star Tan wrote: >> >> >> At 2013-07-14 02:30:07,"Tobias Grosser" <tobias at grosser.es> wrote: >>> On 07/13/2013 10:13 AM, Star Tan wrote: >>>> Hi Tobias, >>> >>> Hi Star, >[...] >>> Before we write a
2012 Jan 16
2
[LLVMdev] Opt pass 'Canonicalize Induction Variables' not working
I am new to LLVM and I've a question about the optimization passes and in particular about the loop transformation passes. I've setup the LLVM tool-chain with Polly installed. The following example is causing problems with me: http://llvm.org/docs/Passes.html#indvars The input is a .c file with the following loops: # 01 Standard, N=100 for (i=0; i<N; i++) b[i] = a[i] + 5; # 02
2012 Jun 24
2
[LLVMdev] [PATCH] cindex.py using find_library
Hello all, Is there a reason why the library location code in cindex py does not use find_library() to locate libclang, like in the attached patch? Without it there were problems locating a versioned libclang.so.1 file on Debian, for example. Cheers, Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL:
2017 Feb 27
2
Compiling LLVM with locally built clang | Errors
Hello, I issued the following command to point the build to use clang and clang++, from a local llvm build directory included in PATH, instead of /usr/bin/{cc,c++}, cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ ../llvm_src The configuration failed with the error stating the compiler didn't recognize '-std=c++11' flag, whereas clang compiled a dummy c++ file with
2018 Sep 20
6
CMake build of LLVM/clang with -DCMAKE_BUILD_TYPE=Release does not create release versions?
Unfortunately, from personal experience, LLVM_PARALLEL_LINK_JOBS appears to have no effect for Visual Studio builds, AND some of the tools linked can take up several GB of RAM, so you'll end up with paging issues. I ended up getting a RAM upgrade in order to sensibly build it (note, I think builds with debug information take more memory than those that don't, and also the clang projects
2003 Nov 27
1
cclust - cindex - binary data
Hi, I'm trying to debug a function I wrote to calculate the cindex for a hierarchical tree. For this it is useful to compare my calculations with those in output from the clustindex function, in the cclust library. There's no way, however, to have the cindex value for a given output of the cclust function, as a NA value is always returned. This happens almost surely because the cindex in
2013 Jul 14
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
Tobi, it looks like this code is the problem: for (std::vector<Value *>::iterator PI = Pointers.begin(), PE = Pointers.end(); ;) { Value *V = *PI; if (V->getName().size() == 0) OS << "\"" << *V << "\""; else OS << "\"" << V->getName() <<