summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
...
* libunwind: check if libatomic is needed at configure timeRoss Burton2025-04-292-1/+39
| | | | | | | | | | Backport a patch submitted upstream to conditionally link explicitly to libatomic, so we don't need to that in the recipe. (From OE-Core rev: 797e645dbcb8a05a2514afc2d5bc2b0b661a0d0e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libunwind: refresh ppc32/musl patchRoss Burton2025-04-291-5/+5
| | | | | | | | | | There was a precedence order problem in the patch so update to the latest version in the pull request. (From OE-Core rev: c64c4ca0c72f6fde3b1d5cfea5803ddf16550fd5) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain/clang: Remove duplicate RANLIB settingKhem Raj2025-04-291-1/+0
| | | | | | | | | Its already assigned couple of lines above (From OE-Core rev: 67a1d55cb50703a3f585521cf44693ade66cc88b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libjpeg-turbo: don't use chrpathSamuli Piippo2025-04-291-5/+3
| | | | | | | | | | | | | | | chrpath doesn't work on mingw32 binaries: | `/build/tmp/work/x86_64-nativesdk-mingw32-w64-mingw32/nativesdk-libjpeg-turbo/3.0.1/image//usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-w64-mingw32/usr/bin/cjpeg.exe' probably isn't an ELF file. | elf_open: Exec format error Instead, use CMake variable to disable RPATH and avoid the useless-rpaths QA error. (From OE-Core rev: 7ffbc913d4b03da4154341f5ca995f767a3bee33) Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-utils: upgrade 1.2.13 -> 1.2.14Michael Opdenacker2025-04-293-82/+2
| | | | | | | | | | | | Remove 2 patches now included upstream. Changelog: https://www.alsa-project.org/wiki/Changes_v1.2.13_v1.2.14 (From OE-Core rev: 23cb89eec07596330a1234f32ff47783c8f00d30) Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-ucm-conf: upgrade 1.2.13 -> 1.2.14Michael Opdenacker2025-04-291-1/+1
| | | | | | | | | Changelog: https://www.alsa-project.org/wiki/Changes_v1.2.13_v1.2.14 (From OE-Core rev: 8a42c65a4db8db6e6a829b66e31b4719b8916883) Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-tools: upgrade 1.2.11 -> 1.2.14Michael Opdenacker2025-04-292-29/+2
| | | | | | | | | | | | Remove 1 patch now included upstream. Changelog: https://www.alsa-project.org/wiki/Changes_v1.2.13_v1.2.14 (From OE-Core rev: 3a394ca7172e80b07f76fb93882d3597d7108219) Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-lib: upgrade 1.2.13 -> 1.2.14Michael Opdenacker2025-04-291-1/+1
| | | | | | | | | Changelog: https://www.alsa-project.org/wiki/Changes_v1.2.13_v1.2.14 (From OE-Core rev: 8518e57a117a67f6a6d963bbb0841a2a40ad7bff) Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers.inc: add entries for virtual/libsdl2Markus Volk2025-04-291-0/+4
| | | | | | | | | | | virtual/libsdl2 can be provided by 'libsdl2' and 'libsdl2-compat' where the latter is a replacement for libsdl2 that uses libsdl3 behind the scenes and should be favored if applicable. (From OE-Core rev: e79d41c9fea112d919fad2603ab0add6c1760757) Signed-off-by: Markus Volk &lt;<a href="mailto:f_l_k@t-online.de">f_l_k@t-online.de</a>&gt; Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mpg123: make use of virtual/libsdl2Markus Volk2025-04-291-1/+1
| | | | | | | | | Fix to ensure it would work with both libsdl2 and libsdl2-compat (From OE-Core rev: 587ccc776e1571f7cccf03104088ecc1e7becf5c) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-numpy: upgrade 2.2.4 -> 2.2.5Trevor Gamblin2025-04-291-1/+1
| | | | | | | | | | | | | | | | Changelog: https://github.com/numpy/numpy/blob/main/doc/changelog/2.2.5-changelog.rst Reproducibility looks OK: |2025-04-24 10:27:00,978 - oe-selftest - INFO - RESULTS - reproducible.ReproducibleTests.test_reproducible_builds: PASSED (1203.06s) |2025-04-24 10:27:00,985 - oe-selftest - INFO - SUMMARY: |2025-04-24 10:27:00,985 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 1233.056s |2025-04-24 10:27:00,985 - oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=1, skipped=0, failures=0, errors=0) (From OE-Core rev: d2ac1be4d2257106c5146ea3c3a136fc4b5116ad) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: fix zst install suffixAntonin Godard2025-04-291-0/+2
| | | | | | | | | | | | | | | The linux-firmware Makefile defines an 'install-zst' rule, but currently fw_compr_suffix() return the '-zstd' suffix when FIRMWARE_COMPRESSION is set to 'zstd' which produces: make: *** No rule to make target 'install-zstd'. Return '-zst' instead to properly run 'make install-zst'. (From OE-Core rev: cc9d972eba1f47fba206665260690ad8de99679f) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libatomic-ops: Update GITHUB_BASE_URINguyen Dat Tho2025-04-291-2/+2
| | | | | | | | | | libatomic-ops moves to new repo https://github.com/ivmai/libatomic_ops according to topic: https://github.com/bdwgc/libatomic_ops/issues/66 (From OE-Core rev: e65452b60d04bae3cdc4f5f5883f60ed78c60594) Signed-off-by: Nguyen Dat Tho <tho3.nguyen@lge.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libarchive: correct upstream version checkAlexander Kanavin2025-04-291-2/+0
| | | | | | | | | | File index works now: http://libarchive.org/downloads/ (From OE-Core rev: 11dfb88badcbb0daf3744eb3ab82bf9290ae5981) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libunwind: use github-releases class to determine latest versionsAlexander Kanavin2025-04-291-2/+3
| | | | | | | (From OE-Core rev: 43ee9831326eac7877b7f148b145c0369c9a06cb) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcf-agent: update SRC_URI to https://gitlab.eclipse.orgAlexander Kanavin2025-04-291-1/+1
| | | | | | | (From OE-Core rev: 5b8190ab58bd235b797b5acfa20e49e28b381990) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-exclusions: correct cve status for 5 entriesDaniel Turull2025-04-261-5/+10
| | | | | | | | | | | | | | In commit 8a7af09feb the CVE_STATUS was copy from the old data for 6.6 kernel, which had backport information. Correcting status to when the fix was introduced and adding references to the fixes. Fixes: 8a7af09febc28477094de0999ab6321d910811b2 Reported-by: Peter Marko <Peter.Marko@siemens.com> (From OE-Core rev: fc3e32bc4cf79ddce0eb9fa409656de4dc0e00ea) Signed-off-by: Daniel Turull <daniel.turull@ericsson.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux/cve-exclusion: Update exclusions after kernel updateMathieu Dubois-Briand2025-04-261-24/+2768
| | | | | | | | | Update CVE exclusions with the update script, as the kernel was updated. (From OE-Core rev: 6e9da1183f50a9ec978d867d7a4f515239fde8d2) Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib.conf: fix typo in commentJoao Marcos Costa2025-04-251-1/+1
| | | | | | | (From OE-Core rev: db2ce170f0381886bab8f05f88a8d8fb1a5844e4) Signed-off-by: Joao Marcos Costa <joaomarcos.costa@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-hypothesis: Update to use the new ptest-python-pytest classLei Maohui2025-04-242-20/+6
| | | | | | | | (From OE-Core rev: e68ad590f9c0b4bcba94ad571553d81e2a7c6f50) Signed-off-by: Lei Maohui <leimaohui@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: Make PATH retain the existing valueMingli Yu2025-04-241-1/+1
| | | | | | | | | | | We may set the PATH variable such as in /etc/environment for ssh session, so make PATH retain the previous existing value to fix the gap. (From OE-Core rev: 4340cd7da25c69424915f29c2bb9531fc33617e6) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest-cargo: handle packageconfig argumentsPeter Marko2025-04-241-1/+2
| | | | | | | | | | | | | | | | | | | | Align cargo options between ptest-cargo and cargo classes. After oe-core commit 16745b20452de60ae2474433cc1a2fb1ed9f6a64 there is a discrepancy between cargo arguments in compile and compile-ptest-cargo steps when packageconfig is used for cargo based recipes. Currently we have to do something like following code to build ptest enabled cargo based recipe: CARGO_BUILD_FLAGS:append:task-compile-ptest-cargo = " ${PACKAGECONFIG_CONFARGS}" Otherwise the options are either doubled in compile step or completely missing in compile-ptest-cargo step. (From OE-Core rev: 98d03d31de4010534b1a00d29409d3486a0ab0b9) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: Fix build break on non-arm/non-x86 systemsKhem Raj2025-04-242-0/+32
| | | | | | | | | | | | | | | Fixes /webkitgtk-2.48.1/Source/WebCore/platform/audio/DenormalDisabler.cpp:94:47: ↪ error: expected ';' after default | 94 | DenormalDisabler::DenormalDisabler() = default | | ^ | | ; (From OE-Core rev: 3325e4e7fc82861abf7505ed4f7926dacab96b30) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: Add pam_env supportMingli Yu2025-04-241-1/+1
| | | | | | | | | | | | | Make setting environment variables in /etc/environment or /etc/security/pam_env.conf take effect for ssh session. [ YOCTO # 15767] (From OE-Core rev: 4e6762f5967b1996cf31ae100fa49e775dfb2866) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sign_rpm.bbclass: fix variable assignment whitespaceYi Zhao2025-04-241-1/+1
| | | | | | | | | | | | Fixes: WARNING: meta/classes/sign_rpm.bbclass:36 has a lack of whitespace around the assignment: 'RPM_SIGN_PACKAGES='1'' (From OE-Core rev: d393539e03b60bf299e2d1c8ac781e0c6f7787b1) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dpkg: drop suffix from version numberYi Zhao2025-04-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | The current dpkg runtime version is generated by 'git describe' command in build-aux/get-version. But since we have made changes to git repo locally, it adds a -dirty suffix to the version number. Add a .dist-version file in the source directory. Then get-version can determine the version through .dist-version instead of "git describe" command, thus removing the -dirty suffix. Before the fix: $ dpkg --version Debian 'dpkg' package management program version 1.22.11-dirty (amd64). After the fix: $ dpkg --version Debian 'dpkg' package management program version 1.22.11 (amd64). (From OE-Core rev: 04d00d69941a9d09bfbb0956186db7a7d0961327) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/populate_sdk.bbclass: drop qemuwrapper-cross from DEPENDSChen Qi2025-04-242-2/+2
| | | | | | | | | | | | | | | | For packages that need qemuwrapper-cross, they should have it in PAKAGE_WRITE_DEPS. Now that we've used 'qemuwrapper-cross' to replace 'qemu-native' for recipes that need qemu-native for their postinsts, and we've now mapped PACKAGE_WRITE_DEPS for nativesdk recipes, these qemuwrapper-cross dependencies can be dropped from image.bbclass and populate_sdk.bbclass. (From OE-Core rev: fbac8d025585fe704f79ccdf00f376f677e3a89d) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spdx: extend CVE_STATUS variablesPeter Marko2025-04-241-0/+5
| | | | | | | | | | | | | If spdx is generated without inheriting cve/vex classes (which is poky default), only explicitly set CVE_STATUS fields are handled. Calculated ones (e.g. from CVE_STATUS_GROUPS) are ignored. Fix this by expanding the CVE_STATUS in spdx classes. (From OE-Core rev: ead9c6a8770463c21210a57cc5320f44f7754dd3) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: extract extending CVE_STATUS to library functionPeter Marko2025-04-243-30/+26
| | | | | | | | | | | | The same code for extending CVE_STATUS by CVE_CHECK_IGNORE and CVE_STATUS_GROUPS is used on multiple places. Create a library funtion to have the code on single place and ready for reuse by additional classes. (From OE-Core rev: 45e18f4270d084d81c21b1e5a4a601ce975d8a77) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats.py: Add tracking of network I/O per interfaceOlga Denisova2025-04-241-2/+41
| | | | | | | | | | | | | | This patch extends SystemStats to collect and store data from /proc/net/dev. It extracts per-interface received and transmitted bytes, calculates deltas between samples, and stores them for further analysis. Useful for identifying network bottlenecks during long-running builds. (From OE-Core rev: 09cbe17e43783fc6b8e3a341d564956452a04c0a) Signed-off-by: denisova-ok <denisova.olga.k@yandex.ru> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats.py: extend diskstats support for NVMe and flexible token countdenisova-ok2025-04-241-2/+2
| | | | | | | | | | | | Added support for NVMe devices in the diskstats regex pattern to ensure stats are properly collected from devices like nvme0n1. Relaxed the check for the number of fields in /proc/diskstats from an exact match (14) to a minimum check (at least 14), to handle kernel variations and additional fields gracefully. (From OE-Core rev: 87a31bc4ca3661aae94cf43f3f579b02f4fb4923) Signed-off-by: denisova-ok <denisova.olga.k@yandex.ru> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Make buildtools respects host CA certificatesChangqing Li2025-04-245-15/+88
| | | | | | | | | | | | | | | | | | | | | | | | To adapt user network enviroment, buildtools should first try to use the user configured envs like SSL_CERT_FILE/CURL_CA_BUNDLE/..., if these envs is not set, then use the auto-detected ca file and ca path, and finally use the CA certificates in buildtools. nativesdk-openssl set OPENSSLDIR as "/not/builtin", need set SSL_CERT_FILE/SSL_CERT_DIR to work nativesdk-curl don't set default ca file, need SSL_CERT_FILE/SSL_CERT_DIR or CURL_CA_BUNDLE/CURL_CA_PATH to work nativesdk-git actually use libcurl, and GIT_SSL_CAPATH/GIT_SSL_CAINFO also works nativesdk-python3-requests will use cacert.pem under python module certifi by default, need to set REQUESTS_CA_BUNDLE (From OE-Core rev: 8a7ec52e9b35654bee48cd948c6c34c63db3e265) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildcfg: get_metadata_git_*: catch also bb.process.NotFoundErrorMartin Jansa2025-04-241-6/+6
| | | | | | | | | | * bb.process.NotFoundError is triggered when e.g. oe.buildcfg.get_metadata_git_branch is called on non-existent directory (From OE-Core rev: 34c1f66c4c689b26a4c3129eb62f4ff9b6ec14be) Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm-sequoia-crypto-policy: Fix build failure on Debian 12+StrongswanYoann Congal2025-04-242-2/+35
| | | | | | | | | | | | | rpm-sequoia-crypto-policy tries to validate the configuration files using host tools. For the Strongswan policy, it uses "ipsec readwriteconf" which is not available on Debian 12 with Strongswan installed. To fix this, add and use an option to skip the problematic validation. (From OE-Core rev: d10ca0fe194b62b2f383be880a008cde2bd0fd4f) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: always depend on the explicit serial console unitsRoss Burton2025-04-231-1/+1
| | | | | | | | | | | | | | | | The systemd-serialgetty recipe generates explicit units for consoles that are defined in SERIAL_CONSOLES, and if that variable is not defined then just produces an empty package. Even when systemd has been configured to use the getty generator, if there are explicit consoles defined then we should respect them. Don't conditionalise the dependency on systemd-serialgetty so that we always pull in the explicit consoles. (From OE-Core rev: a7036173acdb84d516f17257e02a936f04c584d8) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: enable getty generator by defaultRoss Burton2025-04-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until recently, even when the getty generator was disabled in the systemd recipe it was actually still active. This was because the old behaviour was to delete the serial-getty template unit if the generator was disabled, but the systemd-serialgetty package shipped then shipped the same files so the generator continued to run. This was a bug in the original commit[1] so this behaviour has been present since 2016. My recent fixes[2] changed this: if the getty generator was disabled then the generator itself is deleted. This makes the actual behaviour match the intention, but the consequence was to demonstrate that some modern platforms were relying on this unexpected behaviour: specifically the genericarm64 BSP which intends to support a number of virtual and physical boards with a number of serial console ports that are not really suitable to be hardcoded into SERIAL_CONSOLES: - ttyS0 - ttyAMA0 (AMBA PL011 uart) - ttyS2 (BeagleBone Play, S0 and S1 are internal) - hvc0 (KVM) - ttyPS1 (AMD KV260) - And most likely more Restore the existing behaviour by explicitly enabling the serial getty generator: this means that systemd will automatically bring up a getty on the first serial console it finds. In the future we should extend some level of dynamic console-finding to sysvinit-based systems by searching for a console device in inittab, but for now this reverts the unintentional regression. [1] oe-core 2a8d0df47c9 ("systemd: make systemd-serialgetty optional") [2] oe-core 2beb3170af6 ("systemd: if getty generator is disabled remove the generator, not the units") (From OE-Core rev: af15f9d1609708443ed036fdb611cea92f566620) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: re-enable the unit tests that are ignoredDeepesh Varatharajan2025-04-231-100/+0
| | | | | | | | | | | | Some unit tests were previously marked as ignored due to failures in earlier versions of Rust. With the upgrade to Rust 1.85.1, these tests are now passing consistently. They've been re-enabled and verified to run successfully on the latest version. (From OE-Core rev: 65c207fb034848f9ef0de8cf8725c5eded363aca) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: Upgrade 2.13.17 -> 2.13.18Richard Purdie2025-04-231-1/+1
| | | | | | | | Includes fixes for 64 bit time on 32 bit platforms. (From OE-Core rev: f50a33c074a2de99c6b4b889c91c673162ec4040) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-tools: 2.13.14 -> 2.13.15Richard Purdie2025-04-236-68/+81
| | | | | | | | Includes fixes for 64 bit time on 32 bit platforms. (From OE-Core rev: bbb542aff833353dd5645e7f4c279ac3625a416f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: add PACKAGECONFIG for sdl-imageMarkus Volk2025-04-231-0/+1
| | | | | | | | | This allows to enable sdl-image support from a bbappend file (From OE-Core rev: ca848cd15bf61f12cdadf4c94c985f2e87a932c8) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: bundle Clang OpenCL headers into meta-clcDmitry Baryshkov2025-04-232-1/+59
| | | | | | | | | | Add a patch bundling OpenCL headers into meta-clc. This removes extra runtime dependencies when runnign meta-clc compiler. (From OE-Core rev: 8a627d93a6a37382c75ca45f5afb9fec069877f8) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: drop the bindgen patchDmitry Baryshkov2025-04-232-72/+1
| | | | | | | | | | Drop the bingen-target and bindgen-includedir options in favour of the bindgen_clang_args being passed through the meson target file. (From OE-Core rev: efd31bbd52b94ac7633e5c9d1664f2305c074059) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: pass -target and -I to bindgen callsDmitry Baryshkov2025-04-231-0/+1
| | | | | | | | | | | | In order to properly generate Rust bindings for the target systems, we need to pass '-taget foo-linux-gnueabi' flags and a correct include target include path (${STAGING_INCDIR}) to the bindgen. Add those flags to the generated meson target file. (From OE-Core rev: 40008d55c01681c60088e5b7defb0b8513a4ed1c) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Switch prefix mapping to use -ffile-prefix-mapKhem Raj2025-04-236-17/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | -ffile-prefix map is more comprehensive when it comes to reproducible builds and its superset of all prefix-mapping options in compilers This makes is cleaner and workable across gcc and clang, clang does not support -fcanon-prefix-map and it has to be explicitly omitted when using clang. There are lambdas generated in templates by clang which still get the absolute paths despite -fdebug-prefix-map, this helps with that as well. nasm is an outlier and we have fixed it by adding -fdebug-prefix-map option luckily we do not pass DEBUG_PREFIX_MAP to nasm, in all recipes which use nasm either pass -fdebug-prefix-map explicitly to nasm or they rewrite it to use nasm flags syntax. We have discussed this in past [1] [1] https://patchwork.yoctoproject.org/project/oe-core/patch/20230428032030.2047920-1-raj.khem@gmail.com/#10281 (From OE-Core rev: ff73fa7ef7666a6dbe34f15515bc3ab6e574c5b0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Jacob Kroon <jacob.kroon@gmail.com> Cc: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Forward -ffile-prefix-map option to assembler flagsKhem Raj2025-04-232-0/+25
| | | | | | | (From OE-Core rev: a85cccc80aa7e6d6a5850c2d730cba5e1cb60cb3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk.bbclass: handle PACKAGE_WRITE_DEPSChen Qi2025-04-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | We want nativesdk packages to depend on correct recipes introduced by PACKAGE_WRITE_DEPS, so do the same mapping just as we do for DEPENDS. Before this change: nativesdk-glib-2.0 -> qemuwrapper-cross After this change: nativesdk-glib-2.0 -> nativesdk-qemuwrapper-cross This can fix do_populate_sdk failure complaining missing of nativesdk-qemuwrapper. Error message is like below: NOTE: > Executing update_gio_module_cache-nativesdk intercept ... NOTE: Exit code 127. Output: /xxx/lib32-core-image-sato/1.0/intercept_scripts-xxxx/ update_gio_module_cache-nativesdk: 13: nativesdk-qemuwrapper: not found (From OE-Core rev: 89ac78e68c4be6e6163223c99e140e7530a61e8e) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cpio: fix ptest-runner dependencyChen Qi2025-04-231-2/+2
| | | | | | | | | | | | | ptest is only meaningful for target. So we need to specify class-target override to ensure correct dependency. Also, the above DEPENDS:append:class-targets lacks a leading whitespace, add it. (From OE-Core rev: ef705f6969845aa4b28cb2cfb95b0aa0c67c11e3) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/recipes: remove unnecessary qemu inherit and use qemuwrapper-crossChen Qi2025-04-238-16/+13
| | | | | | | | | | | | | | | These classes/recipes inherit qemu.bbclass but do not use anything from it. What they use is qemuwrapper-cross, which is needed at do_rootfs time and needs to be pulled-in by PACKAGE_WRITE_DEPS. Also, in meta/conf/layer.conf, exclude qemuwrapper-cross deps for all arch recipes that depend on it. This it ensure allarch recipes have the same signature across different machines. (From OE-Core rev: 6f3ce94f4c03e7b26f1fcdf78ea969f57717ec56) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.12: cfg: fix iommu configuration for -tiny kernelBruce Ashfield2025-04-233-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Integrating the following commit(s) to linux-yocto/.: 1/1 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: iommu: add config dependencies Date: Sun, 20 Apr 2025 22:28:21 -0400 commit [cfg/intel.scc: Include iommu.scc for Arrowlake boot support] moves the iommu configuration to a location that is included by more BSPs and kernel types. One of those kernel types is the -tiny kernel, which uses a allnoconfig base. Due to the allnoconfig, there are missing dependencies to allow the desired options to be enabled in the final .config Those missing options throw configuration audit warnings By adding the required dependencies to the fragment, it is now standalone and can be included from anywhere without configuration audit warnings being triggered. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] (From OE-Core rev: fdef4e2efa1b7d91e43b1758af667b3bb376fd23) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.12: cfg: Include iommu.scc for Arrowlake boot supportBruce Ashfield2025-04-233-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Integrating the following commit(s) to linux-yocto/.: 1/1 [ Author: Yogesh Tyagi Email: yogesh.tyagi@intel.com Subject: cfg/intel.scc: Include iommu.scc for Arrowlake boot support Date: Mon, 14 Apr 2025 11:55:45 +0530 Move features/iommu/iommu.scc from bsp/intel-common/intel-corei7-64.scc and bsp/intel-x86/intel-x86.scc to cfg/intel.scc to eliminate redundancy and ensure IOMMU support (CONFIG_INTEL_IOMMU=y, etc.) is enabled for genericx86-64 on Intel Arrowlake, resolving boot issues. This changes is needed in 6.12 as well as master branch. https://bugzilla.yoctoproject.org/show_bug.cgi?id=15802 Signed-off-by: Yogesh Tyagi <yogesh.tyagi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] (From OE-Core rev: 7cbdfc1091879ba20ba0c33938eb9814f2be8d0c) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-13 23:51:31 +0000