ARMv61 has backwards compatability with ARMv4 compiled code. We don't have any ARMv61 devices to test on, but everything should work fine with our current build of TurboActivate for ARM.
Tell me if you run into any problems.
ARMv61 support
Thank you very much for the ARMv4 support. It is working nicely. We are looking to expand our device support to ARMv61 architecture as well. Is there anything on the roadmap for ARMv61?
Unfortuntely, when we are trying on our ARMv61 box, we are coming across this error seemingly related to JNA native access.
Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/jna/jna3300932508377462001.tmp: /tmp/jna/jna3300932508377462001.tmp: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1954) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1843) at java.lang.Runtime.load0(Runtime.java:792) at java.lang.System.load(System.java:1060) at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:771) at com.sun.jna.Native.loadNativeLibrary(Native.java:697) at com.sun.jna.Native.<clinit>(Native.java:127) at turboactivate.TurboActivateNative.<clinit>(TurboActivate.java:833) at turboactivate.TurboActivate.SetPDetsLocation(TurboActivate.java:676) at test.client.LicenseChecker.isLicensed(LicenseChecker.java:60) at test.client.MyClient.run(MyClient.java:1293) at test.client.MyClient.main(MyClient.java:1329)
Does that help narrow down the issue at all? Thanks for any help!
Are you using the new JNA library included in the latest TurboActivate package? If so, don't. Unfortunately the guys(s) maintaining JNA decided to remove Linux ARM support from the latest version. The old JNA version you we're using before should work, though.
We've been thinking about making a custom build of the JNA library to continue to support Linux ARM for future version of JNA. We just haven't had the time.
So, use the old JNA -- everything should work.
Thanks for looking into the issue. It turns out it's probably a java issue. We downgraded to java 1.6 from 1.8, which seems to be working fine. Haven't tried 1.7 yet, but we're ok for now.
Great, I'm glad to hear it.