<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/conf, branch walnascar</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=walnascar</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=walnascar'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-09-25T19:25:51+00:00</updated>
<entry>
<title>sanity.conf: Update minimum bitbake version to 2.12.1</title>
<updated>2025-09-25T19:25:51+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>martin.jansa@gmail.com</email>
</author>
<published>2025-09-09T17:17:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0fd54596bb8f4a5651adf8c6bc743d512f963f10'/>
<id>urn:sha1:0fd54596bb8f4a5651adf8c6bc743d512f963f10</id>
<content type='text'>
Needed for multiprocessing module in bb used in the next commit.

It was added to bitbake in 62be9113d98fccb347c6aa0a10d5c4ee2857f8b6
which was backported to 2.12 branch and tagged as 2.12.1

(From OE-Core rev: fcfc3056b0b8d0c63fddd0a7624622aee9a1c2f1)

Signed-off-by: Martin Jansa &lt;martin.jansa@gmail.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>default-distrovars.inc: Fix CONNECTIVITY_CHECK_URIS redirect issue</title>
<updated>2025-09-09T16:30:07+00:00</updated>
<author>
<name>Deepak Rathore</name>
<email>deeratho@cisco.com</email>
</author>
<published>2025-08-29T12:51:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=199b07672708e206a76470fb9ceb5fafbdd845dd'/>
<id>urn:sha1:199b07672708e206a76470fb9ceb5fafbdd845dd</id>
<content type='text'>
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: 894648f4173a8a0e489e720e2b543cd22e39a878)

Signed-off-by: Deepak Rathore &lt;deeratho@cisco.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 60cdf960a3560f391babd559737f1afb31fb2c5c)
Signed-off-by: Deepak Rathore &lt;deeratho@cisco.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>yocto-uninative: Update to 4.9 for glibc 2.42</title>
<updated>2025-08-29T17:02:59+00:00</updated>
<author>
<name>Michael Halstead</name>
<email>mhalstead@linuxfoundation.org</email>
</author>
<published>2025-08-21T22:41:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=36326e581e22af56b0d8f01bdacf19678fa12819'/>
<id>urn:sha1:36326e581e22af56b0d8f01bdacf19678fa12819</id>
<content type='text'>
(From OE-Core rev: adbb7737cbfbe241df514704b9bb237e41505310)

Signed-off-by: Michael Halstead &lt;mhalstead@linuxfoundation.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>yocto-uninative: Update to 4.8 for GCC 15.1</title>
<updated>2025-08-29T17:02:59+00:00</updated>
<author>
<name>Michael Halstead</name>
<email>mhalstead@linuxfoundation.org</email>
</author>
<published>2025-08-21T22:41:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e5a9adf1a5e5be88fc37ac284b2be9065a52ea9a'/>
<id>urn:sha1:e5a9adf1a5e5be88fc37ac284b2be9065a52ea9a</id>
<content type='text'>
(From OE-Core rev: ea3a60aabab3b7b456bd086f9e59b42d9ba62ce3)

Signed-off-by: Michael Halstead &lt;mhalstead@linuxfoundation.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>tune-cortexr52: Remove aarch64 for ARM Cortex-R52</title>
<updated>2025-06-20T16:21:27+00:00</updated>
<author>
<name>Sandeep Gundlupet Raju</name>
<email>sandeep.gundlupet-raju@amd.com</email>
</author>
<published>2025-06-13T18:11:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a727f01635aefe50f586578616fdfdbdb3e9379f'/>
<id>urn:sha1:a727f01635aefe50f586578616fdfdbdb3e9379f</id>
<content type='text'>
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: fd79c20430ad5c540522ddbe72ef235379c628bd)

Signed-off-by: Sandeep Gundlupet Raju &lt;sandeep.gundlupet-raju@amd.com&gt;
Signed-off-by: Sandeep Gundlupet Raju &lt;grsandeep85@gmail.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>gcc: Upgrade to GCC 14.3</title>
<updated>2025-06-20T16:21:27+00:00</updated>
<author>
<name>Deepesh Varatharajan</name>
<email>Deepesh.Varatharajan@windriver.com</email>
</author>
<published>2025-06-12T10:48:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a704e5171ce4f87e27408934b593e5a186ac1960'/>
<id>urn:sha1:a704e5171ce4f87e27408934b593e5a186ac1960</id>
<content type='text'>
GCC 14.3 is a bug-fix release from the GCC 14 branch
containing important fixes for regressions and serious bugs in
GCC 14.2 with more than 211 bugs fixed since the previous release.

https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&amp;resolution=FIXED&amp;target_milestone=14.3

Dropped the below patches:
0026-gcc-Fix-c-tweak-for-Wrange-loop-construct.patch
https://github.com/gcc-mirror/gcc/commit/a9f88741a99ba09b29cc0021499c63ca445393f0

0027-gcc-backport-patch-to-fix-data-relocation-to-ENDBR-s.patch
https://github.com/gcc-mirror/gcc/commit/aa4cd614456de65ee3417acb83c6cff0640144e9

0028-fix-incorrect-preprocessor-line-numbers.patch
https://github.com/gcc-mirror/gcc/commit/8cbe033a8a88fe6437cc5d343ae0ddf8dd3455c8

0001-arm-Fix-LDRD-register-overlap-PR117675.patch
https://github.com/gcc-mirror/gcc/commit/9366c328518766d896155388726055624716c0af

gcc.git-ab884fffe3fc82a710bea66ad651720d71c938b8.patch
https://github.com/gcc-mirror/gcc/commit/ab884fffe3fc82a710bea66ad651720d71c938b8

(From OE-Core rev: aa59bbbbedb25d772648c4cb1498b34b43efb0fb)

Signed-off-by: Deepesh Varatharajan &lt;Deepesh.Varatharajan@windriver.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>glibc-y2038-tests: remove glibc-y2038-tests_2.41.bb recipe</title>
<updated>2025-05-19T15:57:20+00:00</updated>
<author>
<name>rajmohan r</name>
<email>semc.2042@gmail.com</email>
</author>
<published>2025-04-29T07:32:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=958da8c6ad539c66ea34b227d9ce45c5f4aaab83'/>
<id>urn:sha1:958da8c6ad539c66ea34b227d9ce45c5f4aaab83</id>
<content type='text'>
This recipe takes longer time &gt;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.41.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). Maybe we can simply remove the recipe?

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.

(From OE-Core rev: dea859e904d9eacede147a627f4c176433ac9efc)

Signed-off-by: rajmohan r &lt;semc.2042@gmail.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit fbe3679ba3c12c52a502511f5dde91fb4de7a6b6)
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update layer series name for release</title>
<updated>2025-03-29T15:31:15+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-03-29T15:30:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6a79d6f9eb790a9ab7c3176543807e629dd7b5ba'/>
<id>urn:sha1:6a79d6f9eb790a9ab7c3176543807e629dd7b5ba</id>
<content type='text'>
Drop styhead from the layer series name ready for release.

(From OE-Core rev: 56253a6ba8dc2d6c337d947ab40d09d7beeddd24)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sanity.conf: Update minimum bitbake version to 2.12.0</title>
<updated>2025-03-29T15:31:15+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-03-29T15:29:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3d8c4ad2cfa18d50a90115078589f994e41616e7'/>
<id>urn:sha1:3d8c4ad2cfa18d50a90115078589f994e41616e7</id>
<content type='text'>
This should have been 2.11 previously but the numbers got confused.
Correct it for release.

(From OE-Core rev: d4a7c9d1e72dd6e45458ac6590e76f10805c0818)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rust: Upgrade 1.83.0-&gt;1.84.1</title>
<updated>2025-03-27T13:41:58+00:00</updated>
<author>
<name>Deepesh Varatharajan</name>
<email>Deepesh.Varatharajan@windriver.com</email>
</author>
<published>2025-03-27T09:06:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6d78fbe5c5945701b6bd30101da5ce16164f4e6b'/>
<id>urn:sha1:6d78fbe5c5945701b6bd30101da5ce16164f4e6b</id>
<content type='text'>
Rust stable version updated to 1.84.1.
https://blog.rust-lang.org/2025/01/30/Rust-1.84.1.html

Renamed and modified the below patch to adapt the new version.
rv32-cargo-rustix-0.38.37-fix.patch-&gt;rv32-cargo-rustix-0.38.38-fix.patch

Modified the below patches to adapt the new version.
repro-issue-fix-with-cc-crate-hashmap.patch
revert-link-std-statically-in-rustc_driver-feature.patch

Dropped the below patches :
0001-NFC-fix-build-failure-100993.patch
https://github.com/llvm/llvm-project/commit/6ee49080e4bb43efe7ede10bed15935853bbd434

revert-Zdual-proc-macros-additional-check.patch
Issue is fixed in rust-master and the fix is backported in the
subsequent patch of the series.

(From OE-Core rev: 4265f668de8c6708cb3a003ad655559031724149)

Signed-off-by: Deepesh Varatharajan &lt;Deepesh.Varatharajan@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
