Thanks for that Burn. That put me on the right track. Turns out that the libuima.so was a link to a non-existent target so technically speaking you were correct and libuima.so was not in the LD_LIBRARY_PATH.
Having solved that one, the C++ annotator is now trying to load but we spit a different error message now about wrong ELFCLASS64 in respect of libuima.so. The box this is running on has an Athlon 64 bit processor but afaik the OS and installed software is all 32 bit. Sounds now like we need to explicitly build libuima.so as 32 bit. What/where is the configuration switch for that. Many thanks for your help. Justin Johansson -----Original Message----- From: Burn Lewis [mailto:[EMAIL PROTECTED] Sent: Tuesday, 2 September 2008 21:47 To: [email protected] Subject: Re: UIMACPP runtime problem on Linux Justin, I think this means that libuima.so is not in the LD_LIBRARY_PATH ... do you have $UIMACPP_HOME/lib there? If this is not the problem, have you been able to run the examples as described in the README? Burn. On Mon, Sep 1, 2008 at 3:02 AM, Johansson, Justin (Contractor) < [EMAIL PROTECTED]> wrote: > Hi Eddie & others, > > I have previously run the UIMA CPE on Windows with a mix of Java and > C++ annotators with success. > Now having built same annotators for Linux, the UIMA CPE spits when > encountering the first C++ Annotator with message like: > > 'No uima on java.library.path' > > And a stack track indicating exceptions thrown by load (native) > library in java. > > I'm guessing this means uima cannot find libuima.so or such but that > is there in the same directory as the annotator .so > > Interestingly runAECpp MyCppAnnotatorDescriptor.xml works .. the > problem is just when trying to run the whole show. > > Seems like I must be missing something in the UIMA C++ setup for Unix > (Linux). > > Any ideas? > > Thanks in advance, > > Justin Johansson > > > IMPORTANT: This email remains the property of the Australian Defence > Organisation and is subject to the jurisdiction of section 70 of the > CRIMES ACT 1914. If you have received this email in error, you are > requested to contact the sender and delete the email. > > >
