fix the failure when the dynamic loader path is different from the ones in libc #204
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.