$ java -jar JCASScript.jar Exception in thread "main" java.lang.UnsatisfiedLinkError: com.filepool.natives.FPLibraryNative.setLastError(I)V at com.filepool.natives.FPLibraryNative.setLastError(Native Method) at com.filepool.fplibrary.FPLibraryException.retrieveErrorString(Unknown Source) at com.filepool.fplibrary.FPLibraryException. (Unknown Source) at com.filepool.fplibrary.FPLogState. (Unknown Source) at LogStateCommands.initLogState(LogStateCommands.java:43) at Commands. (Commands.java:50) at Casscript.runCasscript(Casscript.java:163) at Casscript.main(Casscript.java:115)
$ java -version java version "1.6.0_0" OpenJDK Runtime Environment (build 1.6.0_0-b11) OpenJDK Client VM (build 1.6.0_0-b11, mixed mode, sharing)
$ uname -a Linux fobos 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010 i686 GNU/Linux
Have you installed the relevant Centera SDK in a directory on the library search path? There are 32 and 64 bit versions available for GCC 3.3 and 4.0 for Linux.
JCASScript is a Java application built using the Centera SDK. The jar file uses the native Centera SDK libraries (in the case of Linux, these are .so shared object libraries).
The current JCASScript distribution for Linux contains the 32 bit SDK libraries for Linux and GCC 3.3. These must be available in a directory on the LD_LIBRARY_PATH of your environment.
I think the PDF that comes with the download clearly states you need to add to the UNIX/Linux PATH and SH_LIB(?) environment variable the location of the executables and libraries.
Have you also put the Centera SDK libraries in that directory? And it looks like you have overwritten (not appended) that directory to the two paths - which probably means it cannot find any of the standard system libraries. Unless you have out all of them /tmp too - which is probably unlikely. At least I hope so!
gstuartemc
2 Intern
•
417 Posts
1544
1
Posted March 11th, 2010 11:00
Mark - there is no real magic to the script, all it does is "java -jar jcasscript.jar".