Closed morph027 closed 11 months ago
Ah, nevermind, using the libsignal builds from @exquo - https://github.com/exquo/signal-libs-build/ it works...not sure whats messed up in my builds, but not scope of this repo :blush:
nevermind, wrong binary 🙈
There is actually a mistake @AsamK in the changelog; the version 0.12.7
requieres the 0.37.0
's libsignal_jni
version and not the 0.36.1
. At least to build a native image with GraalVM
.
the version
0.12.7
requieres the0.37.0
'slibsignal_jni
version and not the0.36.1
. At least to build a native image withGraalVM
.
Which version of GraalVM/which settings are you using to encounter a problem? With GraalVM CE 17.0.9+9.1 (build 17.0.9+9-jvmci-23.0-b22), the local native builds for arm64/aarch64 and amd64/x86_64 linked against libsignal_jni
version 0.36.1 work just fine here (see signal-cli_ubuntu2004_arm64.meta, signal-cli_ubuntu2004_amd64.meta).
Which version of GraalVM/which settings are you using to encounter a problem? With GraalVM CE 17.0.9+9.1 (build 17.0.9+9-jvmci-23.0-b22), the local native builds for arm64/aarch64 and amd64/x86_64 linked against libsignal_jni version 0.36.1 work just fine here (see signal-cli_ubuntu2004_arm64.meta, signal-cli_ubuntu2004_amd64.meta).
Using the latest GraalVM community 21.0.1
against x86_64
(didn't had the time to test it against aarch64
) with no particular settings.
Only works with 0.37.0
from my CI as I said.
Just to be sure we are talking about the same thing. The problem is not about building, it's about running (I should have formulated it better in my previous message).
Native build for 0.12.7 w/ libsignal-client 0.36.1 throws an error: