UnsatisfiedLinkError: No awt in java.library.path about graal HOT 6 OPEN

Thank you greatly for the concise reproducer! Assigning it to @pejovica as he is providing support for AWT.

from graal.

@tabiStein sure, I hope you don't mind that I've re-assigned the ticket to you. Please update the ticket when paketo-buildpacks/native-image#308 is resolved.

from graal.

@tabiStein Is libawt.so next to the built executable? If not, was it listed in the build output as a produced artifact?

from graal.

@pejovica No, the executable is alone in a workspace/ directory.

Yes, I do see libawt.so listed in the built artifacts:
[INFO] [creator] Produced artifacts:
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libawt.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libawt_headless.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libawt_xawt.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libfontmanager.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libfreetype.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libjava.so (jdk_library_shim)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libjavajpeg.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/libjvm.so (jdk_library_shim)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/liblcms.so (jdk_library)
[INFO] [creator] /layers/paketo-buildpacks_native-image/native-image/org.example.App (executable)

I've attached the full output of running mvn -Pnative package, so you can check it in detail:
packageOutput.txt

from graal.

No, the executable is alone in a workspace/ directory.

Well, that's the problem. All produced artifacts are necessary for the executable to work (i.e., it can't work without the listed shared libraries).

Since the build output shows that all required artifacts are produced, and the error corresponds to the fact that the shared libraries are indeed missing when running the executable, there is nothing to fix on the native image side.

I'm guessing this is a bug with what drives the native-image as it doesn't seem to take into account all the artifacts produced by the build.

from graal.

Thanks for the insight @pejovica , I have created a new issue with the Paketo team to see if it's an issue with their buildpack. Paketo Issue 427

If it's alright with you, I would like to keep this issue open until we can identify and verify the fix.

from graal.