similar to: [LLVMdev] LLVMdev Digest, Vol 77, Issue 9

Dear all: I cannot build llvm/clang with the revision r118398 configured with ./configure --enable-optimized --enable-doxygen --with-optimize-option. When I do make I get make[1]: Entering directory `/home/wingsit/llvm/lib/System' llvm[1]: Compiling Atomic.cpp for Release+Asserts build g++: yes: No such file or directory make[1]: ***

Hi Jack, I didn't get this error. Could you try again? Is it one of the release candidates in particular that's failing? -bw On Oct 2, 2010, at 8:04 AM, Jack Howarth wrote: > Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. > > #!/bin/bash -ev > export LD=`xcode-select -print-path`/usr/bin/ld > xcode-select -print-path > ulimit -s

Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. #!/bin/bash -ev export LD=`xcode-select -print-path`/usr/bin/ld xcode-select -print-path ulimit -s `ulimit -s` ulimit -s mv ../clang-2.8 ./tools/clang mkdir ../llvm_objdir cd ../llvm_objdir ../llvm-2.8/configure --prefix=/sw --prefix=/sw --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw

Hi all, After updating llvm+clang to r174701 by issuing make -j8 happiness The build fails with: ... make[2]: Entering directory `/local/csaba/LLVM/build-release/tools/llvm-diff' llvm[2]: Compiling DiffConsumer.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable lli (without symbols) llvm[2]: Compiling CrashDebugger.cpp for Release+Asserts build

Actually it only link the shlib fine. Linking any executable against it fails: llvm[2]: Linking Release+Asserts executable llvm-lto (without symbols) /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts/Release+Asserts/bin/clang++ -fsanitize=address -O3 -Wl,-R -Wl,'$ORIGIN/../lib' -L/home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/lib

I'm trying to customize llvm by adding a header file of my own and tweaking things accordingly. While building, things go well until a certain point where it stops seeing the includes of my file. I'm working on Ubuntu 12.04 with llvm-3.1 on a custom target (mips-like), gcc-4.6 and clang-3.2 (i've tried 3.1 too). >From what i've understood, when it builds the first binaries of

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

Hi, On Linux I observed [root at localhost poolalloc]# find . -name *.a ./Release+Asserts/lib/LLVMDataStructure.a ./Release+Asserts/lib/poolalloc.a ./Release+Asserts/lib/AssistDS.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Asserts/lib/libpoolalloc_rt.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libcount.a On cygwin I observed kpawar at KPAWAR-LT

Hi, Going ahead, the llvm-ld seems to segfault (build on Linux with llvm-ld v3.0svn build): make[2]: Entering directory `/root/code/vmkit/mmtk/mmtk-j3' llvm[2]: Building Debug+Asserts Bytecode Module MMTKRuntime.bc 0 llvm-ld 0x0884c66e 1 llvm-ld 0x0884c3fb 2 0xb7891400 __kernel_sigreturn + 0 3 llvm-ld 0x083be9e9 llvm::isa_impl<llvm::Constant,

Hi Akshat, > Going ahead, the llvm-ld seems to segfault (build on Linux with llvm-ld v3.0svn > build): try updating to latest LLVM from svn - this was fixed a day or two ago. Ciao, Duncan. > > make[2]: Entering directory `/root/code/vmkit/mmtk/mmtk-j3' > llvm[2]: Building Debug+Asserts Bytecode Module MMTKRuntime.bc > 0 llvm-ld 0x0884c66e > 1 llvm-ld 0x0884c3fb

Hello everybody, after moving from OS X to Linux build llvm with asan enabled (I also updated to trunk, but not sure if that's related). However, it's totally possible that I missed a step that I took back when I set this up for me, so I might be doing something very stupid. Anyway, I'm configuring LLVM with ../configure --prefix=/home/kfischer/julia/usr --build=x86_64-pc-linux-gnu

Indeed, removing that flag works fine, the only question is why this is added in tools/llvm-shlib/Makefile in the first place then and what to do about it: ifeq ($(HOST_OS), $(filter $(HOST_OS), Linux GNU GNU/kFreeBSD)) # Don't allow unresolved symbols. LLVMLibsOptions += -Wl,--no-undefined endif On Thu, Nov 21, 2013 at 11:53 AM, Alexander Potapenko <glider at

On Sun, Dec 30, 2012 at 12:19 AM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hello, > > I just applied changes of LLVM 3.2 and it is tested with LLVM 3.2 > downloaded from the LLVM Download Page. > > I just worked for master branch only. > The rest of the other branches need to be changed about this also. > This will be done as soon as possible. >

What I meant to say was that it worked for me on OS X on a slightly older version of LLVM. Anyway, here's the ld line: "/usr/bin/ld" -export-dynamic -z relro --hash-style=gnu --build-id --eh-frame-hdr -m elf_x86_64 -shared -o /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/lib/

On Thu, Nov 21, 2013 at 6:18 AM, Keno Fischer <kfischer at csail.mit.edu> wrote: > Hello everybody, > > after moving from OS X to Linux build llvm with asan enabled Sorry, I failed to parse this. You're compiling Clang on Linux, and OSX is unrelated, right? > (I also updated > to trunk, but not sure if that's related). However, it's totally possible > that I

> Try building with "make VERBOSE=1", which will show you the > command-lines passed to the compiler/linker. Post the output here. there you go: > cafxx at ubuntu:~/Projects/llvm2/lib/Transforms/cgf$ make VERBOSE=1 > llvm[0]: Compiling CGFPass.cpp for Debug+Asserts build (PIC) > if g++ -I/home/cafxx/Projects/llvm2/include >

Yeah, it's not linking the runtime because you're building a shared library. This is totally ok. In this case there are undefined __asan_* symbols that are resolved when an instrumented binary loads your library. What's wrong here is that some flag passed to ld prevents it from creating undefined symbols (--no-undefined?). This flag must be removed when building with ASan. This

Hi, I tried building again with the latest llvm. I am getting another seg fault: make[2]: Entering directory `/root/code/vmkit/mmtk/java' Buildfile: /root/code/vmkit/mmtk/java/build.xml main: [javac] /root/code/vmkit/mmtk/java/build.xml:4: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1

Hi Nicolas, I am so sorry for the questions. According to you, I built VMKit2 on Ubuntu11.10-desktop-amd64 on Intel(R) Corei5, and the previous problem solved. But another one appeared! With the following configuration: elaheh at elaheh-Lenovo-G470:~/Desktop/vmkit2$ ./configure --with-llvmsrc=/home/elaheh/Desktop/llvm/ --with-llvmobj=/home/elaheh/Desktop/llvm/

Hello Peng Yu, I found the same error on my Macbook Air. This was my first trying on MacOS X. Troubleshooting this might take sometime. Only thing I can say now that klang is tested successfully on Ubuntu with - LLVM 3.2 official release on LLVM download page - LLVM svn latest update Clang compile produces an error message on MacOS X with the LLVM svn latest update I am trying to find the