Build native image for signal-cli v0.12.2 #1333
-
|
Hello everybody, has anyone had success building a x86-64 native image for signal-cli v0.12.2? I tried it both with the GraalVM v22.3.2 Community Edition as well as with the newer GraalVM JDK 17.0.8+9.1. While both builds succeed, the resulting binary then throws the following error when it gets invoked: Not sure if this is of relevance, but here is the output of Unfortunately, I do not have much experience with GraalVM, so any help is greatly appreciated! Thanks, |
Beta Was this translation helpful? Give feedback.
Answered by
m-ueberall
Oct 1, 2023
Replies: 2 comments 4 replies
-
Yes (see https://media.projektzentrisch.de/temp/signal-cli/).
Let's start with the above library–which one did you use during your builds (the one provided by this repository or one you built yourself/downloaded elsewhere)? The above copy should still exist on your file system; therefore,
If the library in use requires a newer glibc, but your version of glibc is |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for your reply! I am using the shared object provided by this repository.
I am using glibc 2.31. Unfortunately, the Do you use the provided |
Beta Was this translation helpful? Give feedback.
4 replies
-
That shared object provided by this repository is too new for your glibc (there are a couple of issues discussing this, see e.g. issue #643).
The GraalVM binary is nearly statically linked (in that it still requires the glibc) and it also contains a copy of all referenced dynamically linked libraries during the build (e.g.,
No, because the builds explicitly target Ubuntu 20.04/Focal Fossa that comes with glibc 2.31; as explained in the |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks for the detailed explanation - very much appreciated! Up to now, I didn't need to replace the That's probably a stupid question, but where do I need to place the self compiled I used What am I doing wrong here? |
Beta Was this translation helpful? Give feedback.
-
It's possible (and somewhat likely) that the build environment/resulting library was still compatible in the beginning, yes. But this should have changed about half a year ago, if I recall correctly? Anyways, …
… have a look at this comment which explains the idea and this comment which demonstrates all the basic steps that are still valid as of today in discussion #1230 (regardless of the Linux distribution, the steps remain the same, of course). EDIT1: Remember to better checkout a proper version tag, not master/head as shown above. 😁 |
Beta Was this translation helpful? Give feedback.
Answer selected by
bbernhard
-
|
Thanks a lot for your detailed answer - very much appreciated! It worked like a charme :) |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible (and somewhat likely) that the build environment/resulting library was still compatible in the beginning, yes. But this should have changed about half a year ago, if I recall correctly? Anyways, …
… have a look at this comment which explains the idea and this comment which demonstrates all the basic steps that are still valid as of today in discussion #1230 (regardless of the Linux dis…