awslabs
fix the failure when the dynamic loader path is different from the ones in libc
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.
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.
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.