Skip to content

Build and load arm64 native libraries of java-runtime-interface-client #276

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

Closed
wants to merge 2 commits into from
Closed

Build and load arm64 native libraries of java-runtime-interface-client #276

wants to merge 2 commits into from

Conversation

zsombor-balogh
Copy link
Contributor

Issue #, if available:

#275 (comment)

Description of changes:

Executing aws-lambda-java-runtime-interface-client (v 2.0.0) with the arm64 architecture on Lambda results in exception when trying to load the native libraries used by the module:

Failed to load the native runtime interface client library /aws-lambda-runtime-interface-client.glibc.so. Exception: /tmp/.aws-lambda-runtime-interface-client: /tmp/.aws-lambda-runtime-interface-client: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform)
Failed to load the native runtime interface client library /aws-lambda-runtime-interface-client.musl.so. Exception: /tmp/.aws-lambda-runtime-interface-client: /tmp/.aws-lambda-runtime-interface-client: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform)

The reason of the exception is that the runtime-interface-client jar doesn't contain the prebuilt native libraries for arm64 only for x86_64.

With this change the libraries will be built for both architectures and loaded at bootstrap.

Testing

Built locally and created a container image function using the local artifact then invoked successfully.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant