similar to: [LLVMdev] llvm-config --libs failed

Thank you, now it is more clear whats going on. There is a line: /bin/sh: /home/wdanilo/dev/llvm/src/projects/Debug+Asserts/bin/llvm-config: No such file or directory but why it is searching for it in that directory? (all makefile configs, are default configs) Below, there is full output of make: >> make VERBOSE=1 for dir in lib tools; do \ if ([ ! -f $dir/Makefile ] || \ command

Wojciech Daniło <wojtek.danilo.ml at gmail.com> writes: > Hi! > I'm trying to use the LLVMProject toolchain (according to this page: > http://llvm.org/docs/Projects.html). > I created a project "test" with kaleidoscope example source code from: > http://llvm.org/docs/tutorial/LangImpl3.html > It compiles successfully with: clang++ -g -O3 toy.cpp `llvm-config

I have noticed that I was installing LLVM according to: http://llvm.org/docs/GettingStarted.html#getting-started so it was no the 3.1 but the 3.2 version from svn (trunk 167573). Maybe in the svn, not stable version, there is a bug? 2012/11/9 Wojciech Daniło <wojtek.danilo.ml at gmail.com> > Does anybody have Idea why I get such error? The LLVM is compiled from > source - is is the

Does anybody have Idea why I get such error? The LLVM is compiled from source - is is the newest version (3.1) from http://llvm.org/releases/ (from 22 may 2012) I created project in llvmsrc/projects/test (as copy of sample project) and I get these errors while attaching LLVM lbraries :( 2012/11/8 Wojciech Daniło <wojtek.danilo.ml at gmail.com> > Thank you, now it is more clear whats

If anyone is interested in this topic, I filled a bug here: http://llvm.org/bugs/post_bug.cgi 2012/11/9 Wojciech Daniło <wojtek.danilo.ml at gmail.com> > I have noticed that I was installing LLVM according to: > http://llvm.org/docs/GettingStarted.html#getting-started > so it was no the 3.1 but the 3.2 version from svn (trunk 167573). > Maybe in the svn, not stable version,

Hi! I'm trying to learn LLVM and I want to compile the Kaleidoscope compiler. according to: http://llvm.org/docs/tutorial/LangImpl3.html I'm compiling it with: clang++ -g -O3 test.cpp `llvm-config --cppflags --ldflags --libs core` -o toy and it indeed works. The problem is that when using eclipse it forces me to divide the compilation into two steps: g++ -O0 -g3 -Wall -c

On Thu, Apr 29, 2010 at 6:31 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Wed, Apr 28, 2010 at 10:48 AM, Yuri <yuri at tsoft.com> wrote: >> Jeffrey Yasskin wrote: >>> >>> We currently use two different techniques to get whole libraries >>> included into the .so. On Linux (gnu ld and gold), we pass >>> --whole-archive, while on

Hi all, (Sorry if the answer to this is obvious - and thanks in advance~) Short version: linker error of _backtrace from LLVMSystem.a building a dynamic library embedding LLVM/clang, both against the OSX 10.4 sdk. Long version: I've just tried rebuilding my project using the 2.6 release, using the following commands to try and force LLVM to build against the OSX 10.4 sdk (I am

Jeffrey Yasskin wrote: >> Would you try the patch at >> http://codereview.appspot.com/download/issue968046_1.diff? It should >> make the BSDs fall into the same path as Linux, and since you use gnu >> ld, that should work for you. >> > > Ping? > Sorry for the delay. Here is what I am getting after applying the patch: gmake[2]: Leaving directory

On Tue, May 4, 2010 at 5:31 PM, Yuri <yuri at tsoft.com> wrote: > Jeffrey Yasskin wrote: >>> >>> Would you try the patch at >>> http://codereview.appspot.com/download/issue968046_1.diff? It should >>> make the BSDs fall into the same path as Linux, and since you use gnu >>> ld, that should work for you. >>> >> >> Ping?

This was replaced by having a #<num> referenced by the object. Kind of like how metadata is referenced. -bw On Feb 3, 2013, at 4:50 PM, Sean Silva <silvas at purdue.edu> wrote: >> To use an attribute group, an object references the attribute group's ID: >> >> attribute_group_ref := attrgroup(<attrgroup_id>) > > Is this unused now? I don't see

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

On Oct 25, 2009, at 1:58 PM, Graham Wakefield wrote: > Hi all, > > (Sorry if the answer to this is obvious - and thanks in advance~) > > Short version: > linker error of _backtrace from LLVMSystem.a building a dynamic > library embedding LLVM/clang, both against the OSX 10.4 sdk. > > Long version: > I've just tried rebuilding my project using the 2.6 release,

On Tue, Nov 6, 2012 at 6:38 AM, Wojciech Daniło <wojtek.danilo.ml at gmail.com> wrote: > Hi! > I'm trying to learn LLVM and I want to compile the Kaleidoscope compiler. > according to: > http://llvm.org/docs/tutorial/LangImpl3.html > > I'm compiling it with: > clang++ -g -O3 test.cpp `llvm-config --cppflags --ldflags --libs core` -o > toy > > and it

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:

LGTM. I will commit. On Oct 10, 2012, at 1:20 PM, Shuxin Yang <shuxin.llvm at gmail.com> wrote: > Hi, > > The attached is the fix to radar://11663049. The optimization can be outlined by following rules: > > (select (x != c), e, c) -> select (x != c), e, x), > (select (x == c), c, e) -> select (x == c), x, e) > where the <c> is an integer

You need to link in the libclang* as well. On 7/10/2012 1:22 PM, NY Knicks Fan wrote: > Hi Ashok, > > $ cd bin/bin > $ ./llvm-config --ldflags --libs > -L/home/ubuntu/bin/lib -ldl -lpthread > -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler > -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter > -lLLVMX86Desc -lLLVMX86Info

Hi Ashok, $ cd bin/bin $ ./llvm-config --ldflags --libs -L/home/ubuntu/bin/lib   -ldl -lpthread -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMJIT -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInstrumentation -lLLVMInterpreter

I'm linking a program (my ellsif driver) that basically brings in most of the LLVM stuff: bitcode reading, optimizations, linking, and target code generation. All of a sudden, I'm getting the following when I run: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions -O5 <premain>: CommandLine Error: Argument 'machine-licm' defined more than once!

Hi, For the record, adding UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/ was insufficient to restrict the .a/.o files to link against the 10.4 sdk, but env MACOSX_DEPLOYMENT_TARGET=10.4 make did the trick. Thanks! On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > > Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > >> >> On Jan 14, 2009, at 12:44 PM,