similar to: [LLVMdev] cmake patch to build other targets

i just tried to build llvm-3.0rc2 on my powerpc (G4) but without success. My toolchain (CRUX PPC 2.7): gcc-4.5.3, binutils-2.21.1, glibc-2.12.2, libffi-3.0.10 my llvm config: ./configure --prefix=/usr --mandir=/usr/man \ --enable-shared \ --enable-libffi --enable-optimize \ --enable-targets=all \ --enable-threads --enable-pic --enable-jit \

Hi all, I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build. *** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o

Hi, I noticed that klibc started crashing on 64-bit MIPS and in my quest to fix the bug I got a bit carried away and fixed a few other things as well. Here are various miscellaneous MIPS patches, although the first patch is the important one. Thanks, James *** BLURB HERE *** James Cowgill (5): mips64: compile with -mno-abicalls mips: use -Ttext-segment when linking shared library

I constructed an LLVM 2.7 VS solution with cmake, but it has 66 projects: ALL_BUILD, ".\ALL_BUILD.vcproj" BrainF, "examples\BrainF\BrainF.vcproj" Fibonacci, "examples\Fibonacci\Fibonacci.vcproj" FileCheck, "utils\FileCheck\FileCheck.vcproj" HowToUseJIT,

Maurice Gittens wrote: > Hi all, > > I just svn-updated the 2.5 branch on my machine and I noticed this > warning during the build. > > *** Warning: Linking the shared library > /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool > *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o >

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> [ brutal-snip ] >> ... >>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more >>>

I'm looking into the possibility of building the libLTO plugin on Linux, and got tangled up in the build system. Currently, tools/Makefile only includes 'lto' when the OS equals Darwin, while tools/lto/Makefile has an if-statement that builds libLTO as a static library on non-Darwin systems. If I try to build libLTO as a dynamic library on Linux, it works fine, but I get an

Hi, While building svn using CMake on an Ubuntu 9.04 system (gcc 4.3.3, binutils 2.19.1, 32-bit kernel and libs): Linking CXX executable ../../bin/llvm-dis [ 93%] Built target llvm-dis Scanning dependencies of target llc [ 93%] Building CXX object tools/llc/CMakeFiles/llc.dir/llc.cpp.o Linking CXX executable ../../bin/llc /usr/bin/ld: error in ../../lib/./LLVMX86AsmPrinter.o(.eh_frame); no

One thing that helps me understand complex software is a dependency graph. I found an LLVM dependency graph at https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies but it's really messy and hard to follow. From that graph I made a cleaner graph by hand (attached)... sorry about the fax-quality scan. But I have some questions about it... -

With reference to the following thread: http://lists.llvm.org/pipermail/llvm-dev/2016-January/094100.html I am having the same issue. First I did a git pull of all the relevant directories and then doing a cmake: cmake -DLLVM_ENABLE_DOXYGEN=ON -DLLVM_ENABLE_WERROR=OFF -DLLVM_TARGETS_TO_BUILD="X86" ../llvm and followed by make: [ 22%] Built target LLVMVectorize [ 25%] Built target

Thanks for the suggestion, Andre. I downloaded GNAT GPL 2007, and followed the directions on your web page. Now I get a lot of C++ errors. In fact, the output I captured to a log file is over six megabytes just from the start of the problem command to the termination of the make. I'm obviously not going to include it all here, but the command and the first few errors are copied below.

hello, I'm attempting to build the inferno source tree using either of native LTO or jit'd bins and having no obvious luck. im using macports (current as of this email) llvm-2.5 and llvm-gcc on a macbook pro (x86) following the inferno directions verbatim will use 'cc' as the compiler and just works. the build tools are different from the naive build tools as follows:

hi all, I'm trying to write an LLVM-based interpreter for a small DSL that we have. The language is very simple (essentially a calculator), but I'd like it to execute efficiently. I've been following the tutorial, and have the following code for instantiating an ExecutionEngine: #include <LLVM\ExecutionEngine\JIT.h> #include

Hi, The test-suite expects to be built standalone but it looks like you have it in the same tree as LLVM. You'll need to remove it. From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Peter Teoh via llvm-dev Sent: 28 February 2016 14:31 To: llvm-dev at lists.llvm.org Subject: [llvm-dev] [cfe-dev] [3.8 Release] We have branched With reference to the following thread:

I checkout LLVM and clang from SVN, then use CMake to generate project files for Visual Studio 2010 (I started with 2008). The LLVM project compiles successfully and gives me all the tools including Clang. For a few tests, I compile C++ code with Clang which if I need to I link, I use MinGW's ld passing all the relevant object files and libraries including correctly ordering the start-up code

On Sat, Nov 29, 2008 at 9:17 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > I'm looking into the possibility of building the libLTO plugin on Linux, > and got tangled up in the build system. > > Currently, tools/Makefile only includes 'lto' when the OS equals Darwin, > while tools/lto/Makefile has an if-statement that builds libLTO as a > static library on

On Thu, Jul 30, 2009 at 11:03 PM, james northrup<northrup.james at gmail.com> wrote: > CC="p llvm-gcc-4.2 `llvm-config --cflags` -march=i386  --emit-llvm -O0 >  -c -I$PLAT/include -I$ROOT/include -I$ROOT/utils/    include" > LD="p llvm-ld `llvm-config --ldflags --libs all  `" > AR="p llvm-ar crvs" Using llvm-ar+llvm-ld is likely to give you bad

I think we've just forgotten to update that part of the instructions. Having the test-suite at projects/test-suite was harmless to the old autoconf and LLVM 3.7.x's cmake builds because it didn't actually cause the test-suite to be built. The CMakeLists.txt that have been added to the test-suite now cause it to be built by LLVM's build system which introduces the build failure. We

Hello, I downloaded LLVM 2.6 and was attempting to compile it with TDM-GCC 4.4.1-tdm2-sjlj + cmake 2.6.4 and this happened: =============Console=================== C:\projects\game-editor\LLVM\build-root>mingw32-make [ 2%] Built target LLVMSystem [ 5%] Built target LLVMSupport [ 7%] Built target tblgen [ 7%] Built target intrinsics_gen [ 10%] Built target LLVMCore [ 12%] Built target

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd