I've gotten my front-end to compile with the 2.6 branch and with trunk (not with both; I have to fiddle with a few things when switching), and it refuses to give me an execution engine. My link flags include everything coming from "llvm-config --libs". Nevertheless, the error string coming back from ExecutionEngine::create is: JIT has not been linked in Is this a known problem? Is there something I should be doing that I wasn't doing in 2.5?
Hi, #include "JIT.h" will do. Cheers, Axel. On 2009-10-06 03:09, Kenneth Uildriks wrote:> I've gotten my front-end to compile with the 2.6 branch and with trunk > (not with both; I have to fiddle with a few things when switching), > and it refuses to give me an execution engine. > > My link flags include everything coming from "llvm-config --libs". > Nevertheless, the error string coming back from > ExecutionEngine::create is: > > JIT has not been linked in > > Is this a known problem? Is there something I should be doing that I > wasn't doing in 2.5? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
On Mon, Oct 5, 2009 at 8:27 PM, Axel Naumann <Axel.Naumann at cern.ch> wrote:> Hi, > > #include "JIT.h" will do.Thanks. That was exactly what I needed to progress to the next error ("Unable to find target for this triple (no targets are registered)") As soon as I get this front-end working with the trunk, I'll start submitting patches that add calls to the C-API; my front-end generates code-generation-code that relies on it rather heavily, and there are gaps I'd like to fill in.