-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GR-58059] Statically Linked native image does not produce/embed all the needed .so next to the executable #8911
Comments
Thank you for reaching out, we'll take a look into this shortly |
FWIW, |
Sorry, I couldn't reproduce this issue locally. |
@oubidar-Abderrahim Sure, clone this repo, and checkout the Once compiled, the native executable does not 'embed'/link the .so, and it fails at runtime with Checkout |
A bit more of context, after installing
|
I was able to statically build the repo you shared, I believe this is an issue of the version of musl toolchain used. Static image are currently working with v10.2.1
Also make sure to follow the instruction at: https://www.graalvm.org/22.1/reference-manual/native-image/StaticImages/ |
I can build too! But can you run it without any error with missing awt for example? |
Sorry, I wasn't clear enough, I was able to both build and run the application statically, without any AWT errors |
Here is my version
Did you build with graalvm CE? |
01-Army of Me.mp3.zip
You should see the fail once the code reaches something that needs awt Thanks again ! |
Hello,
I have a working little app (Spring Boot 3, maven, latest graalvm CE, linux) here.
I want to compile it with musl, so it's more portable regarding glibc.
At the moment, the executable is produced without any problem in github actions (and on my work station) : the executable and all the
.so
are well produced intarget
.I have installed
musl
andzlib
like stated here , and have changed my maven configuration :The compilation is succesful, but the
.so
are not next to the executable (expected, as I imagine they are "embedded" in the final executable), then the app fails withCaused by: java.lang.UnsatisfiedLinkError: No awt in java.library.path
for example, and so on.I can see in the log that the
.so
are not producedAm I missing something ? Thanks !
The text was updated successfully, but these errors were encountered: