-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Missing static JDK libraries compiled against musl #4645
Comments
It appears the files are taken from the JVMCI builds, https://github.com/graalvm/labs-openjdk-11/. Should this issue be moved there? |
I believe if you're cross-compiling, you'll need to install musl toolchain for aarch64 in your $TOOLCHAIN_DIR (as explained in https://www.graalvm.org/22.1/reference-manual/native-image/StaticImages/) |
@oubidar-Abderrahim yes, I did. However, that toolchain itself is generic. It doesn't contain the JDK-static libraries compiled against musl, those are only available for linux-amd64 in that download. |
I have the same issue for 22.3.r17
We shall have a buildpack for this which can be used together with spring-boot-maven-plugin The issue is with nik |
Any news here .. when this will be fixed |
The NIK issue has been fixed in 22.3.1. The original issue, I'm not sure. The instructions mentioned there imply that static linking against musl is not supported on ARM. |
Any builder image used in packets buildpack https://github.com/paketo-buildpacks/native-image is to recent in context of libc Version requirement that it simply can not be successful executed on aws lambda due to bindings to libc version not matched on lambda base images(to old) aws/aws-lambda-base-images#59 (comment) How shall build and deploy to lambda using bionic /glibc 2.7 |
If this issue is still relevant in the latest GraalVM versions, please create a new issue for it and follow the template provided. Thank you |
hello, i've run into the same problem when trying to compile static NI on aarch64 platform. |
@oubidar-Abderrahim This is still relevant for upstream issues, can we re-open? |
Specifically, this is needed for #8350 |
I created a new issue which was closed: #10375. Update: Ah I realise now that I created a “bug” issue and I should create feature request issue. Will do that momentarily. @sgammon, why are the files for graalvm compiled against musl required for getting cosmo to work? Shouldn’t then the cosmo linked files be also added? |
@spockz Cosmo is based on Musl, and these libraries are needed to actually compile a GraalVM libc layer intended to be used with Cosmo. |
Describe the issue
I am trying to make a static image which, as per instructions, needs musl as the libc implementation. When doing this
native-image
fails, unable to find the static jdk libraries it needs in$JAVA_HOME/lib/static/linux-aarch64/musl
. This directory is missing, only aglibc
directory exists.Steps to reproduce the issue
Please include both build steps as well as run steps
Describe GraalVM and your environment:
The text was updated successfully, but these errors were encountered: