FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

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

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 commented Nov 7, 2024
edited
Loading

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.

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.

Copy link
Copy Markdown
Contributor

Careful, this might break in other distros.
We need to find a more reliable way to get the path of the dynamic loader.
Unfortunately, I don't have access to a ubuntu machine (and I don't work at aws anymore). But please, try to see if there's a more robust way of fixing this.

Thank you for the PR.

Copy link
Copy Markdown
Author

Hi @marcomagdy, thanks for your suggestion. I have made a new change to make it use the dynamic loader from libc when the one from ldd is not found in libc. I think it is more robust now.

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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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


Back | FazBrowse Home | New Git URL