← Back to team overview

sikuli-driver team mailing list archive

[Question #190141]: can't start Sikuli on rhel6 64 bit

 

New question #190141 on Sikuli:
https://answers.launchpad.net/sikuli/+question/190141

Hi, 

I can't run sikuli properly on my rhel6 64bit , the error message i got:
[info] locale: en_US
Exception in thread "main" java.lang.UnsatisfiedLinkError: /home/username/apps/sikuli/Sikuli-IDE/libs/libJXGrabKey.so: /home/username/apps/sikuli/Sikuli-IDE/libs/libJXGrabKey.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch)
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1703)
	at java.lang.Runtime.load0(Runtime.java:770)
	at java.lang.System.load(System.java:1003)
	at com.wapmx.nativeutils.jniloader.NativeLoader.loadLibrary(NativeLoader.java:44)
	at org.sikuli.script.internal.hotkey.LinuxHotkeyManager.<clinit>(LinuxHotkeyManager.java:25)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:169)
	at org.sikuli.script.internal.hotkey.HotkeyManager.getInstance(HotkeyManager.java:54)
	at org.sikuli.ide.SikuliIDE.installCaptureHotkey(SikuliIDE.java:797)
	at org.sikuli.ide.SikuliIDE.initHotkeys(SikuliIDE.java:808)
	at org.sikuli.ide.SikuliIDE.<init>(SikuliIDE.java:701)
	at org.sikuli.ide.SikuliIDE.getInstance(SikuliIDE.java:138)
	at org.sikuli.ide.SikuliIDE.main(SikuliIDE.java:973)

I tried to solve the problem by doing as this post suggested:
https://answers.launchpad.net/sikuli/+question/152727

 but I failed to build JXGrabkey from source:
$ g++ -Wall -fPIC -c *.cpp
JXGrabKey.h:19:17: error: jni.h: No such file or directory
JXGrabKey.h:20:22: error: X11/Xlib.h: No such file or directory
JXGrabKey.cpp:25:24: error: X11/keysym.h: No such file or directory
In file included from JXGrabKey.cpp:22:
JXGrabKey.h:28: error: ‘KeyCode’ does not name a type
JXGrabKey.h:29: error: ‘Mask’ does not name a type
JXGrabKey.h:32: error: variable or field ‘getOffendingModifiers’ declared void
JXGrabKey.h:32: error: ‘Display’ was not declared in this scope
JXGrabKey.h:32: error: ‘_dpy’ was not declared in this scope
JXGrabKey.h:33: error: ‘Display’ was not declared in this scope
JXGrabKey.h:33: error: ‘_dpy’ was not declared in this scope
JXGrabKey.h:33: error: ‘XErrorEvent’ was not declared in this scope
JXGrabKey.h:33: error: ‘_event’ was not declared in this scope
JXGrabKey.h:33: error: initializer expression list treated as compound expression
JXGrabKey.h:34: error: variable or field ‘printToDebugCallback’ declared void
JXGrabKey.h:34: error: ‘JNIEnv’ was not declared in this scope
JXGrabKey.h:34: error: ‘_env’ was not declared in this scope
JXGrabKey.h:34: error: expected primary-expression before ‘const’
JXGrabKey.h:35: error: variable or field ‘grabKey’ declared void
JXGrabKey.h:35: error: ‘JNIEnv’ was not declared in this scope
JXGrabKey.h:35: error: ‘_env’ was not declared in this scope
JXGrabKey.h:35: error: expected primary-expression before ‘key’
JXGrabKey.h:36: error: variable or field ‘ungrabKey’ declared void
JXGrabKey.h:36: error: ‘JNIEnv’ was not declared in this scope
JXGrabKey.h:36: error: ‘_env’ was not declared in this scope
JXGrabKey.h:36: error: expected primary-expression before ‘key’
JXGrabKey.h:45: error: expected constructor, destructor, or type conversion before ‘void’
JXGrabKey.h:52: error: expected constructor, destructor, or type conversion before ‘void’
JXGrabKey.h:59: error: expected constructor, destructor, or type conversion before ‘void’
JXGrabKey.h:66: error: expected constructor, destructor, or type conversion before ‘void’
JXGrabKey.h:73: error: expected constructor, destructor, or type conversion before ‘void’
JXGrabKey.cpp:35: error: expected constructor, destructor, or type conversion before ‘*’ token
JXGrabKey.cpp:50: error: expected constructor, destructor, or type conversion before ‘void’
JXGrabKey.h:33: warning: ‘xErrorHandler’ defined but not used

is there any workaround??





-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.