Weekly release: merge master-next to master (2026-W20)#15673
Closed
rpcme wants to merge 56 commits into
Closed
Conversation
Add XXH_NO_INLINE_HINTS=1 when DEBUG_BUILD is enabled to prevent xxhash inline optimization issues during debug builds. Co-authored-by: BinCaoWR <BinCaoWR@users.noreply.github.com> Rebased from #15583
…lti-lib crashes
Remove 001-shared-static-crt-libs.patch which forces BUILD_SHARED_LIBS=OFF
for aws-crt-cpp and aws-c-iot, statically embedding them into each IoT
service .so. Combined with -Wl,-Bsymbolic, this isolates CRT globals per
.so, causing NULL allocator crashes when applications link against 2+ IoT
service libraries (e.g., IotSecureTunneling + IotJobs).
Root cause: file-static variables like s_aws_json_module_allocator in json.c
are only initialized by ApiHandle in the main binary. With -Bsymbolic and
static CRT, each .so copy stays NULL.
Restore FILES:${PN}-dev for CRT shared libs and RCONFLICTS:${PN} for
aws-c-iot (as the recipe had before commit 210a44d). The CRT now builds
as shared libraries with a single process-wide copy, which is how the
upstream SDK is designed to work.
Fixes: #15582
Reverts: 210a44d ("aws-iot-device-sdk-cpp-v2: disable sanitizer checks")
…esent
The SDK recipe with build-deps enabled bundles its own aws-c-iot and
declares RCONFLICTS:${PN} = "aws-c-iot". When the CI tries to install
both aws-iot-device-sdk-cpp-v2-ptest and aws-c-iot-ptest into the same
test image, opkg cannot resolve the conflict.
Add mutual exclusion logic (same pattern as aws-cli-v2/aws-cli) to
drop aws-c-iot from the recipe list when aws-iot-device-sdk-cpp-v2 is
being tested.
Refs: #15582
Remove the redundant inline Python BBFILES += lines that iterate over BBFILE_COLLECTIONS to add dynamic-layers recipes. This mechanism predates BBFILES_DYNAMIC and is entirely redundant — the only dynamic-layers subdirectory (virtualization-layer) is already handled by the existing BBFILES_DYNAMIC entry. Also fix the BBFILES_DYNAMIC glob pattern from /*/*/*.bb to recipes-*/*/*.bb for consistency with the main BBFILES pattern. Fixes: #15595
The version of recipe aws-iot-device-sdk-cpp-v2-samples-mqtt5-pubsub is `1.0' $ ls tmp/work/corei7-64-wrs-linux/aws-iot-device-sdk-cpp-v2-samples-mqtt5-pubsub/ 1.0 Because no PV in recipe, use 1.0 as default Due to recipe aws-iot-device-sdk-cpp-v2-samples-mqtt5-pubsub and aws-iot-device-sdk-cpp-v2-samples-fleet-provisoning use the same source of aws-iot-device-sdk-cpp-v2, ... aws-iot-device-sdk-cpp-v2-version.inc <-- aws-iot-device-sdk-cpp-v2-samples.inc <-- aws-iot-device-sdk-cpp-v2-samples-mqtt5-pubsub.bb aws-iot-device-sdk-cpp-v2-version.inc <-- aws-iot-device-sdk-cpp-v2-samples.inc <-- aws-iot-device-sdk-cpp-v2-samples-fleet-provisoning.bb ... Originally, we have [99fcca1 aws-iot-device-sdk-cpp-v2-version.inc: explicitly set PV] to fix the issue, but commit [c656353 aws-iot-device-sdk-cpp-v2: upgrade 1.35.1 -> 1.40.1] dropped PV setting and caused regression, this patch explicitly rename recipe with version to avoid regression at next upgrade After apply this patch: $ ls tmp/work/corei7-64-wrs-linux/aws-iot-device-sdk-cpp-v2-samples-mqtt5-pubsub/ 1.40.1 Same to recipe aws-iot-device-sdk-cpp-v2-samples-fleet-provisoning Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Member
Author
|
Closing in favor of a new PR with conflicts resolved. |
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
4 participants
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.
Weekly Release Merge
Merge
master-nextintomasterfor the week 20 release.Note: This is a merge commit (not fast-forward) because
masterandmaster-nextdiverged due to rebased commits pushed directly tomasteron May 5. Going forward, all changes should flow throughmaster-nextfirst to maintain fast-forward capability.Changes included (since last master release)