linux/poky.git/meta/conf, branch scarthgap-5.0.16

conf/bitbake.conf: use gnu mirror instead of main server

2025-10-13T19:42:58+00:00

ftp.gnu.org is the main server of the GNU project, however download speed can vary greatly based on one's location. Using ftpmirror.gnu.org should redirect the request to the closest up-to-date mirror, which should result sometimes in significantly faster download speed, depending on one's location. This should also distribute the traffic more across the mirrors. This information was sourced from https://www.gnu.org/prep/ftp.html . (From OE-Core rev: ef14bcae0f3f27acdd4e591fac69515aa912f194) Signed-off-by: Gyorgy Sarvari Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit d8c6f01d7467e018aa0ed27a87850d9e4434a47a) Signed-off-by: Steve Sakoman

sanity.conf: Update minimum bitbake version to 2.8.1

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

Needed for multiprocessing module in bb used in the next commit. It was added to bitbake in 62be9113d98fccb347c6aa0a10d5c4ee2857f8b6 which was backported to 2.8 branch and tagged as 2.8.1 (From OE-Core rev: 95888aa944847cf6dbfac501997a3e2980344b66) Signed-off-by: Martin Jansa Signed-off-by: Steve Sakoman

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

package: export debugsources in PKGDESTWORK as json

2025-07-07T14:42:58+00:00

The source information used during packaging can be use from other tasks to have more detailed information on the files used during the compilation and improve SPDX accuracy. Source files used during compilation are store as compressed zstd json in pkgdata/debugsources/$PN-debugsources.json.zstd Format: { binary1: [src1, src2, ...], binary2: [src1, src2, ...] } I checked the sstate size, and it slightly increases using core-image-full-cmdline: without patch: 2456792 KB sstate-cache/ with patch: 2460028 KB sstate-cache/ (4236 KB or 0.17%) (From OE-Core rev: c507dcb8a8780a42bfe68b1ebaff0909b4236e6b) Adaptations to match spdx in scarthgap: change BP to PF CC: Mathieu Dubois-Briand CC: Richard Purdie (From OE-Core rev: cba53212f5debf897752453364b9756a05c197de) Signed-off-by: Daniel Turull 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

tune-cortexr52: Remove aarch64 for ARM Cortex-R52

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

Remove aarch64 for ARM Cortex-R52 processor as it supports only 32-bit ISA but not 64-bit ISA. Also update ARMPKGARCH for cortexr52hf. (From OE-Core rev: 8ee21ec40e9f25ee97ec077b93751fea14b66e32) Signed-off-by: Sandeep Gundlupet Raju Signed-off-by: Sandeep Gundlupet Raju 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