fix the failure when the dynamic loader path is different from the ones in libc by AlbertXingZhang · Pull Request #204 · awslabs/aws-lambda-cpp · GitHub
Skip to content

fix the failure when the dynamic loader path is different from the ones in libc#204

Open
AlbertXingZhang wants to merge 2 commits into
awslabs:masterfrom
AlbertXingZhang:patch-1
Open

fix the failure when the dynamic loader path is different from the ones in libc#204
AlbertXingZhang wants to merge 2 commits into
awslabs:masterfrom
AlbertXingZhang:patch-1

Conversation

@AlbertXingZhang

@AlbertXingZhang AlbertXingZhang commented Nov 7, 2024

Copy link
Copy Markdown

Issue #, if available:
In Ubuntu 24.04, the dynamic loader path from the ldd command is different from the paths in dpkg-quey.
image
So the current packaging process fails because the packager could not find the dynamic loader.

Description of changes:
The PR changes it to using the dynamic loader from libc if the one from ldd is not found in libc.

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

@marcomagdy

Copy link
Copy Markdown
Contributor

@AlbertXingZhang

Copy link
Copy Markdown
Author

@AlbertXingZhang AlbertXingZhang changed the title fix the failure when the dynamic loader path is different from the one from libc fix the failure when the dynamic loader path is different from the ones in libc Nov 8, 2024
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.

2 participants