I encountered a packaging problem when migrating my lambdas from al2 to al2023
[100%] Built target query
Failed to identify, locate or package the loader. Please file an issue on Github!
make[3]: *** [query/CMakeFiles/aws-lambda-package-query.dir/build.make:70: query/CMakeFiles/aws-lambda-package-query] Error 1
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
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.
I encountered a packaging problem when migrating my lambdas from al2 to al2023
Here is my ldd
linux-vdso.so.1 (0x0000ffffa2292000) libcurl.so.4 => /lib64/libcurl.so.4 (0x0000ffffa2192000) libz.so.1 => /lib64/libz.so.1 (0x0000ffffa2151000) libcrypto.so.3 => /lib64/libcrypto.so.3 (0x0000ffffa1c00000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x0000ffffa1800000) libm.so.6 => /lib64/libm.so.6 (0x0000ffffa20a0000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000ffffa1baf000) libc.so.6 => /lib64/libc.so.6 (0x0000ffffa1632000) libnghttp2.so.14 => /lib64/libnghttp2.so.14 (0x0000ffffa1b5e000) libidn2.so.0 => /lib64/libidn2.so.0 (0x0000ffffa1b0d000) libpsl.so.5 => /lib64/libpsl.so.5 (0x0000ffffa1acc000) libssl.so.3 => /lib64/libssl.so.3 (0x0000ffffa152e000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000ffffa14bd000) /lib/ld-linux-aarch64.so.1 (0x0000ffffa2245000) libunistring.so.2 => /lib64/libunistring.so.2 (0x0000ffffa130c000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000ffffa120a000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000ffffa1a8b000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000ffffa11c9000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000ffffa1188000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000ffffa1147000) libresolv.so.2 => /lib64/libresolv.so.2 (0x0000ffffa1104000) libselinux.so.1 => /lib64/libselinux.so.1 (0x0000ffffa10b1000) libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x0000ffffa1000000)on al2023 /lib64 is a symlink
and this is what rpm returns
So, here is a one-liner that works for me, tested only with al2023-arm64.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.