linux/poky.git/meta/conf/distro/include, branch scarthgap

yocto-uninative: Update to 5.1 for glibc 2.43

2026-05-04T12:57:32+00:00

(From OE-Core rev: fd94d49fa9b053105ddc725d5e3024582395a373) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie (cherry picked from commit c1fb515f2a88fa0a0e95529afc07a99db001af0e) [YC: Remove duplicated line in commit message] Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

yocto-uninative: Update to 5.0 for needed patchelf updates

2026-05-04T12:57:32+00:00

Solves some segfaults on relocated qemu-img binaries. [YOCTO #16003] (From OE-Core rev: 756f29ce4dcd0dad05e3f5bfccbcfe1ca3a0b112) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie [YC: removed extra line from commit message upstream commit b322bc5387f3 ("meta/conf/distro/include/yocto-uninative.inc")] Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

default-distrovars.inc: Fix CONNECTIVITY_CHECK_URIS redirect issue

2025-09-09T16:08:09+00:00

The default CONNECTIVITY_CHECK_URIS uses "https://yoctoproject.org/connectivity.html" which redirect to "https://www.yoctoproject.org/connectivity.html". Some network configurations with proxies or restricted internet access don't handle HTTP redirects properly during the sanity check phase, causing build failures with: ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Fetcher failure for URL: 'https://yoctoproject.org/connectivity.html'. URL doesn't work. Updated the default URL to use the final destination directly to avoid redirect-related connectivity check failures. Also updated SDK test cases in https.py to use the corrected URL for consistency. (From OE-Core rev: bd624ebbcf4e6d7a24c4ab232ca2e138b1ac3433) Signed-off-by: Deepak Rathore Signed-off-by: Richard Purdie (cherry picked from commit 60cdf960a3560f391babd559737f1afb31fb2c5c) Signed-off-by: Deepak Rathore Signed-off-by: Steve Sakoman

yocto-uninative: Update to 4.9 for glibc 2.42

2025-09-01T15:30:56+00:00

(From OE-Core rev: 9f0cc5fe65f71cf1d28b7a34272f29db03dc6778) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

yocto-uninative: Update to 4.8 for GCC 15.1

2025-09-01T15:30:56+00:00

(From OE-Core rev: 02b285fb0258587e9b78ee4b1b4b2eea0e0a4b3e) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

libpng: Add ptest

2025-06-20T15:38:12+00:00

Install libpng test-suite to run it as a ptest. As the test-suite takes more than 30 seconds to run, add libpng-ptest to PTESTS_SLOW in ptest-packagelists.inc (From OE-Core rev: 1b52b7ebe5f8fb490088622181cdb95e6b7f5a29) Signed-off-by: Poonam Jadhav Signed-off-by: Steve Sakoman

gcc: Upgrade to GCC 13.4

2025-06-20T15:38:12+00:00

This is a bugfix release in GCC13 release series 100+ bugfixes https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=13.4 Dropped the following patches: 0028-gcc-Fix-c-tweak-for-Wrange-loop-construct.patch https://github.com/gcc-mirror/gcc/commit/179dc0f0fe01012675c1b430591b9891ce96c26e gcc.git-ab884fffe3fc82a710bea66ad651720d71c938b8.patch https://github.com/gcc-mirror/gcc/commit/5ceea2ac106d6dd1aa8175670b15a801316cf1c9 #GCC 13.3 #GCC 13.4 #Diff No. of expected passes 148863 149440 +577 No. of unexpected failures 14 14 0 No. of expected failures 1415 1414 -1 No. of unresolved testcases 25384 25660 +276 No. of unsupported tests 2692 2689 -3 (From OE-Core rev: 7af83314fea5948937403b5d59ba5df6fecdd81a) Signed-off-by: Deepesh Varatharajan Signed-off-by: Steve Sakoman

glibc-y2038-tests: remove glibc-y2038-tests_2.39.bb recipe

2025-05-19T15:32:49+00:00

This recipe takes longer time >20min when bitbake for package write stage. When cross-verified for longer time duration, found that do_check() stage taking 20min while other stages completes before 6min. This recipe gives only below two test binaries in the packages to test (ptest: glibc-y2038-tests): io/ftwtest io/ftwtest-time64 The above test binaries are already included for testing in recipe glibc-testsuite_2.39.bb. It is by now well established that glibc itself works as it should, that all affected 32 bit targets are configured to use 64 bit time_t, and that any lingering y2038 issues are in components other than the c library, and usually come from C programming mistakes (e.g. storing timestamps in long). So this recipe seems to be redundant and can be removed. Review comments for fixing above longer time duration ended up in removing this recipe as a proposal is below https://lists.openembedded.org/g/openembedded-core/topic/112188476#msg214636 Removed lines having reference to glibc-y2038-tests in the files. For master branch requested for integration and below is the link https://lists.openembedded.org/g/openembedded-core/message/215655 (From OE-Core rev: b214cc84a922f7a3fb7ebbc501189ce25e8bd2bd) Signed-off-by: rajmohan r Signed-off-by: Steve Sakoman

yocto-uninative: Update to 4.7 for glibc 2.41

2025-04-07T13:34:44+00:00

(From OE-Core rev: 7626067432743657e9c536ca16a2dac513ba4929) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa Signed-off-by: Steve Sakoman

yocto-uninative: Update to 4.6 for glibc 2.40

2024-09-19T12:11:35+00:00

(From OE-Core rev: 0a8ba360f111d379af436de86e0a990be02910bb) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie (cherry picked from commit b29bfd333dffe635ab67475dcd8d22ad8b114c84) Signed-off-by: Steve Sakoman