[LLVMdev] Error while creating ExecutionEngine
Bill Wendling
isanbard at gmail.com
Sun Oct 26 15:59:21 PDT 2008
I've never encountered that error message before. Here's what the 'web
had to say about it:
http://www.openldap.org/lists/openldap-technical/200801/msg00244.html
http://www.gamedev.net/community/forums/topic.asp?topic_id=320771
They might help?
-bw
On Oct 26, 2008, at 2:36 PM, bhavani krishnan wrote:
>
> Thanks Bill! But it does not work. I get the error given below when
> I try to load LLVMExecutionEngine.o in the opt command.
>
> Error opening '../../../build/Release/lib/
> LLVMExecutionEngine.o': ../../../build/Release/lib/
> LLVMExecutionEngine.o: only ET_DYN and ET_EXEC can be loaded
> -load request ignored.
>
> Any ideas?? Please help me out here.
>
> Thanks,
> Bhavani
>
> --- On Sun, 10/26/08, Bill Wendling <isanbard at gmail.com> wrote:
>
>> From: Bill Wendling <isanbard at gmail.com>
>> Subject: Re: [LLVMdev] Error while creating ExecutionEngine
>> To: bhavi63 at yahoo.com, "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu
>> >
>> Date: Sunday, October 26, 2008, 6:46 AM
>> On Oct 25, 2008, at 9:51 PM, bhavani krishnan wrote:
>>
>>> Hi,
>>>
>>> I am completely new to llvm. I am trying to build an
>> optimization
>>> pass. I need to interpret some instructions in the
>> pass. To begin
>>> with, I used the exact same code as HowtoUseJIT
>> example. It compiles
>>> fine. While executing using opt, I get the following
>> error at the
>>> point where th executionengine is created:
>>> opt: symbol lookup error: ../../../Release/lib/Try.so:
>> undefined
>>> symbol:
>> _ZN4llvm15ExecutionEngine6createEPNS_14ModuleProviderEbPSs
>>>
>>> I tried looking in the archives but could not find any
>> similar
>>> problem.
>>> Please let me know what I am doing wrong. Please let
>> me know if it
>>> is possible to create an object of executionengine in
>> the
>>> optimization pass?
>>>
>> I'm not 100% sure, but I think that you will have to
>> have opt load up
>> the LLVMExecutionEngine.o library.
>>
>> -bw
>
>
>
More information about the llvm-dev
mailing list