search for: forceinterpreterlinking

...) || > g++ -g -O0 toy-example26.cpp -o toy-example26 \ || `/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/bin/ llvm-config --cppflags --ldflags --libs core jit native` || Undefined symbols: || "_LLVMLinkInInterpreter", referenced from: || (anonymous namespace)::ForceInterpreterLinking::ForceInterpreterLinking() in ccXf1BAH.o || ld: symbol(s) not found || collect2: ld returned 1 exit status Note, `/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/ bin/llvm-config --cppflags --ldflags --libs core jit native` gives (formating by me) -I/Users/albert/NoTime...

...after producing object files (.o) without comment. When I enter the following (from the documentation): g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o `llvm-config --libs engine bcreader scalaropts` I get: HowToUseJIT.o(.gnu.linkonce.t._ZN44_GLOBAL__N_HowToUseJIT.cpp_DD76033A_C9DF05AB23ForceInterpreterLinkingC1Ev+0x1e): In function `(anonymous namespace)::ForceInterpreterLinking::ForceInterpreterLinking()': /usr/home/x/llvm1.9/include/llvm/ModuleProvider.h:71 undefined reference to `llvm::LinkInInterpreter()' Any help appreciated Raphael -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/...

Look at what is in <llvm source root>/examples/Kaleidoscope/toy.cpp. This is the final version of the tutorial and worked the last time I played with 2.6. Garrison On Jan 23, 2010, at 12:21, ALbert Mietus wrote: > I ask for advice, for TheExecutionEngine === NULL, > >>> Which result's in a null-pointer for "TheExecutionEngine"; which >>> explains

...-O0 toy-example26.cpp -o toy-example26 \ > || `/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/bin/llvm-config --cppflags --ldflags --libs core jit native` > || Undefined symbols: > || "_LLVMLinkInInterpreter", referenced from: > || (anonymous namespace)::ForceInterpreterLinking::ForceInterpreterLinking() in ccXf1BAH.o > || ld: symbol(s) not found > || collect2: ld returned 1 exit status > > Note, `/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/bin/llvm-config --cppflags --ldflags --libs core jit native` gives > (formating by me) &g...

I ask for advice, for TheExecutionEngine === NULL, >> Which result's in a null-pointer for "TheExecutionEngine"; which >> explains the bus-errror .. Reid Kleckner wrote: > Try changing the above line to: > std::string str; > TheExecutionEngine = > EngineBuilder(OurModuleProvider).setErrorStr(str).create(); > cout << str << '\n';

...2) In-tree linking doesn't work. I'm not sure why out-of-tree linking with llvm-config works better than in-tree linking. I'll need to take a look a Reid's scripts. 3) Judging from Reid's bug reports, linking 'interpreter' doesn't seem to be enough to get the ForceInterpreterLinking() function. I have no idea what's going on here--this code was added after llvm- config was committed. I want to get these issues sorted out in time for LLVM 1.7. For LLVM 1.8, we can look into re-writing llvm-config as a C++ program (to remove llvm-config's dependency on Perl, allo...