From af2b968cb3d3fa5c345b41658c52ba2867be0924 Mon Sep 17 00:00:00 2001 From: "riseproject-dev[bot]" <330740410+riseproject-dev[bot]@users.noreply.github.com> Date: Tue, 29 Sep 2026 07:59:11 +0000 Subject: [PATCH 1/2] awslambdaric: Add version 4.1.0 Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com> --- docs/packages/awslambdaric.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/packages/awslambdaric.yaml b/docs/packages/awslambdaric.yaml index 5588d847e82..bef7c452e16 100644 --- a/docs/packages/awslambdaric.yaml +++ b/docs/packages/awslambdaric.yaml @@ -50,3 +50,4 @@ versions: - filename: awslambdaric-4.0.4-cp314-cp314t-manylinux_2_38_riscv64.manylinux_2_39_riscv64.whl sha256: 97c5ca8edc6a6e5c4e65f11503e047e36a5f5813e120073834b68b39bf56a6cc requires-python: '>=3.9' +- version: 4.1.0 From 22a1492c27f9553b629656512c6cc563fd5c22ef Mon Sep 17 00:00:00 2001 From: Ludovic Henry Date: Thu, 1 Oct 2026 08:17:18 +0000 Subject: [PATCH 2/2] awslambdaric: carry forward the backward-cpp riscv64 build patch to 4.1.0 The nightly-upgrade bot bumped docs/packages/awslambdaric.yaml to 4.1.0 without creating a matching patches/awslambdaric/4.1.0/ directory, so the workflow's unconditional 'git apply .../00*.patch' step failed with no matching file. scripts/preinstall.sh's aws-lambda-cpp CMake invocation is unchanged between 4.0.4 and 4.1.0 (verified against the 4.1.0 tag), so the existing patch applies as-is. --- ...uild-on-backward-cpp-s-unknown-archi.patch | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 patches/awslambdaric/4.1.0/0001-Don-t-fail-the-build-on-backward-cpp-s-unknown-archi.patch diff --git a/patches/awslambdaric/4.1.0/0001-Don-t-fail-the-build-on-backward-cpp-s-unknown-archi.patch b/patches/awslambdaric/4.1.0/0001-Don-t-fail-the-build-on-backward-cpp-s-unknown-archi.patch new file mode 100644 index 00000000000..2e4d4c9a943 --- /dev/null +++ b/patches/awslambdaric/4.1.0/0001-Don-t-fail-the-build-on-backward-cpp-s-unknown-archi.patch @@ -0,0 +1,42 @@ +From 8508835032bf42315bf84331ed11bcec53d6a5c0 Mon Sep 17 00:00:00 2001 +From: Ludovic Henry +Date: Sun, 6 Sep 2026 13:07:57 +0200 +Subject: [PATCH] Don't fail the build on backward-cpp's unknown-architecture + warning on riscv64 + +aws-lambda-cpp vendors backward-cpp for enhanced stack traces on crash and +compiles it under its own -Wall -Wextra -Werror. backward-cpp's +SignalHandling::handleSignal() dispatches the crash program-counter lookup on +the target architecture (__aarch64__, __arm__, __ppc__, ...) and has no case +for riscv64 (__riscv), so it falls into the catch-all #else branch: a bare +#warning plus an unused ucontext_t* variable in that branch. Neither is a +correctness bug - the fallback just leaves error_addr unset, so the crash +handler still fires and unwinds the stack, only without pinpointing the +faulting instruction - but -Werror turns both into hard compile errors and +the build never reaches the extension. + +-Wno-error=cpp neutralises the #warning-as-error; -Wno-error=unused-variable +covers the now-unused uctx in that same branch. Both stay warnings (visible in +the build log) rather than being silenced outright. + +Upstream-Status: To upstream [not submitted from this automated port run; needs a pull request against aws/aws-lambda-python-runtime-interface-client] +--- + scripts/preinstall.sh | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/scripts/preinstall.sh b/scripts/preinstall.sh +index fdc436c..71fb871 100755 +--- a/scripts/preinstall.sh ++++ b/scripts/preinstall.sh +@@ -50,7 +50,7 @@ else + cd ./aws-lambda-cpp-$AWS_LAMBDA_CPP_RELEASE/build + + $CMAKE .. \ +- -DCMAKE_CXX_FLAGS="-fPIC" \ ++ -DCMAKE_CXX_FLAGS="-fPIC -Wno-error=cpp -Wno-error=unused-variable" \ + -DCMAKE_INSTALL_PREFIX="$ARTIFACTS_DIR" \ + -DENABLE_LTO=$ENABLE_LTO \ + -DCMAKE_MODULE_PATH="$ARTIFACTS_DIR"/lib/pkgconfig && \ +-- +2.50.1 (Apple Git-155) +