Open muka opened 7 years ago
Found a solution, reporting the steps here
jffi
from a PI, I was expecting it to be cross-built but was not the caseunzip archive/jffi-arm-Linux.jar
and mv jni <your-path>
java -jar <app.jar> -Djava.library.path="<your-path>/jni"
Would make sense to add to the documentation?
It would be best if we just added the built JAR. NB: jnr-constants would also need to be updated, if you're using that project.
@headius @tduehr Do either of you have a Raspberry Pi to build on?
I do but it's one of the first gen and I don't have it setup currently. I might be able to get my hands on a 2nd gen as well but I don't exactly know when I can get to it. If there's a qemu config to emulate one, that'd be easiest for me.
It seems there is one in the main qemu project now. I'll take a poke when I can.
this may not be entirely relevant, but I've run into the same problem on my tinkerboard using openjdk to run logstash - same architecture, different distribution (armbian). I ensured that I had the following os packages installed, and that seemed to clear it up:
default-jdk-headless
default-jre-headless
libjnr-ffi-java
libjffi-java
libjffi-jni
libasm-java
libjnr-x86asm-java
you might need to do the same if dockerizing for armv7l
Hi, I am using this library (actually
jnr-unixsocket
) to create a dbus connection in a docker container.It works outside of a docker container, while fails in it with:(UPDATE) It seems not to work in the host system and neither in the containerInspecting the container fs I find the library. I tried changing the
java.io.tmpdir
but no luck and also set 777 to avoid any permission error.Relevant sources are here for reference
Do you have any suggestion?
I would be glad to help testing if needed.
Thanks
UPDATE2: Related to #30