summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
...
* tcmode-default: eliminate needless binutils version defaultsRandy MacLeod2025-03-171-6/+0
| | | | | | | | | Manually setting preferred version is not required so remove that for binutils. (From OE-Core rev: a6961e13d3dd4d94dbb771328e6c67c101a157be) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: eliminate needless 'go' defaultsRandy MacLeod2025-03-081-15/+0
| | | | | | | | | Manually setting preferred version/provider is not required so remove that for 'go'. (From OE-Core rev: f01aa20752a4435dd10a523aa01d40addb1cd8d0) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: eliminate needless gdb, qemu defaultsRandy MacLeod2025-03-081-11/+0
| | | | | | | | | | | | | Manually setting preferred version/provider is not required so remove that for gdb and qemu as a first step of cleaning up this file. This PREFERRED_VERSION list dates back to 2006, which is an era where several versions of a given recipe was a common occurence. (From OE-Core rev: 4f22ca1233b390308f8266bafe96efaee0631cf4) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fastfloat: add recipeMarkus Volk2025-03-071-0/+1
| | | | | | | | | | | | | | | | A header-only library for fast number parsing An older version of this recipe is included in meta-oe, since fastfloat is also used by libplacebo. If the recipe is accepted, I will send a patch for removal there. The reason why this is needed in oe-core is the upcoming vte release, which uses fastfloat but pulls it as a wrap-based subproject by default. (From OE-Core rev: 09aba21e7eb51b2ebe5448135c8c2438985240fe) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mirrors: rationalise Debian mirrorsRoss Burton2025-03-061-1/+1
| | | | | | | | | | | | | | | Change DEBIAN_MIRROR to point at the canonical server, deb.debian.org. This is a CDN-backed server using network magic to load balance across the planet so there's no need to set a slew of regional mirrors. Also add a more recent snapshot.debian.org from the beginning of 2025. (From OE-Core rev: 3d95d45836accd29916dd8cb9bfe624d63d6c202) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.82.0->1.83.0Deepesh Varatharajan2025-03-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rust stable version updated to 1.83.0. https://blog.rust-lang.org/2024/11/28/Rust-1.83.0.html Renamed and modified the below patch to adapt the new version. rv32-cargo-rustix-0.38.34-fix.patch->rv32-cargo-rustix-0.38.37-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: zlib-off64_t.patch https://github.com/madler/zlib/commit/a566e156b3fa07b566ddbf6801b517a9dba04fa3kq Because of the following commit , https://github.com/rust-lang/rust/commit/68034f837a39387e49fc7d7c5b088f5372a1127e when we enable lib32, getting build failure because there is a check for target support for "-Zdual-proc-macros" flag not functioning properly when lib32 is enabled in the build environment. So for now reverting this commit and bring back the previous behavior, where the "-Zdual-proc-macros" flag is always added for building proc macros, regardless of the target architecture's support. This would bypass the check introduced in the patch, allowing the build to proceed without error, even when building for a 64-bit architecture with lib32 enabled. (From OE-Core rev: 40d8dafdf556d7ce79c12a6de872193be9a0928a) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Start to separate out gcc related variable definitionsRichard Purdie2025-03-055-41/+100
| | | | | | | | | | | | To be able to switch toolchains, we need to separate out the gcc definitions into seperate include files. This patch starts that process. Whilst the include is still hardcoded for now, it allows developers to start experimenting with this locally more easily and stops people reinventing this patch. A sample clang configuruation is also included which I was using for experimentation. (From OE-Core rev: be063d58c0985a2c43c16302efb44706fbf3f1b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: change email addressMarta Rybczynska2025-03-031-3/+3
| | | | | | | | (From OE-Core rev: 3e09e4d9a19cec68a41faaea555a1ed7b76e576e) Signed-off-by: Marta Rybczynska <marta.rybczynska@ygreky.com> Signed-off-by: Marta Rybczynska <mrybczynska@syslinbit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: bump GOVERSION to 1.24.0hongxu2025-03-031-1/+1
| | | | | | | | | | | | | | Due to we have upgraded go to 1.24.0, we should also bump GOVERSION to fix preferred version warning ... WARNING: preferred version 1.22% of go not available (for item go) WARNING: versions of go available: 1.24.0 ... (From OE-Core rev: 939449cfcb4a920132145d2ad1212bac3acb1baa) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/documentation.conf: remove OE_IMPORTSRoss Burton2025-02-281-1/+0
| | | | | | | | | | | | oe-core no longer supports OE_IMPORTS[1], so remove the documentation. [1] oe-core 1f56155e ("base: Switch to use addpylib directive and BB_GLOBAL_PYMODULES") (From OE-Core rev: d1388e0958c8013179a948e08bf989c07f8654ca) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-roman-numerals-py: add recipeTrevor Gamblin2025-02-271-0/+1
| | | | | | | | | | | | roman-numerals-py is a module providing utilities for working with well-formed Roman numerals. python3-sphinx relies on this now, so add it as a recipe. (From OE-Core rev: 43b4e995769de54e47b0a98ce841b143a877f87d) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache.conf: Add include_file_ctime to sloppinessFabio Berton2025-02-271-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When multiple recipes are built in parallel, Ccache sometimes refuses to lookup some objects in cache, leading to undesired cache misses. The root cause of this is an interaction between the way how bitbake constructs a recipe sysroot and Ccache's `include_file_ctime` check. Whenever bitbake creates a recipe's sysroot it hardlinks the files provided by a recipes dependencies. Adding a hardlink to a file changes it's ctime which in turn leads Ccache to believe that the file was modified thus aborting the cache lookup. To avoid this situation, add `include_file_ctime` to the list of checks that should be ignored using the Ccache sloppiness configuration option [1]. Example of a log entry that Ccache ignores a file: / |recipe-sysroot/usr/include/bits/pthread_stack_min.h had status change |near or after invocation (ctime 1739822508.107677255, invocation time |1739822507.970071107) \ 1 - https://ccache.dev/manual/4.10.2.html#config_sloppiness (From OE-Core rev: 4899698297c7783e02aba5388e0469cc83bd2f70) Signed-off-by: Fabio Berton <fabio.berton@criticaltechworks.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Update to 4.7 for glibc 2.41Michael Halstead2025-02-251-5/+5
| | | | | | | (From OE-Core rev: 84fa232cc1b50f0d15c090377659d6aa7a065b1d) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: remove AUTHOR[doc]Ross Burton2025-02-211-1/+0
| | | | | | | | | | | | | The variable was mostly removed in oe-core 9d5edd12 but the documentation remained. [ YOCTO #15758 ] (From OE-Core rev: 6aab808bb9adee8e2409c23f49c6bc021007f1d8) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.81.0->1.82.0Deepesh Varatharajan2025-02-201-1/+1
| | | | | | | | | | | | | | | Rust stable version updated to 1.82.0. https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html Renamed the below patch to adapt the new version. rv32-cargo-rustix-0.38.28-fix.patch->rv32-cargo-rustix-0.38.34-fix.patch Dropped: rv32-rustix-libc-backend.patch [addressed with rv32-cargo-rustix-0.38.34-fix.patch] (From OE-Core rev: cfa431e734a642796140347f09c3c54b41a7bb75) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sassc, libsass: add recipesSimone Weiß2025-02-181-1/+3
| | | | | | | | | | | Those have been in meta-oe, but are needed for libadwaita upgrade. Also updates libsass to newest version. I can take care of those recipes for now. (From OE-Core rev: 0a1d3607da7bb7c586c69cefadf8ade52c7b1987) Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm-sequoia: New recipe for version 1.7.0Zoltán Böszörményi2025-02-181-0/+1
| | | | | | | | | | | | rpm 4.20 removed the built-in code to handle signed packages and uses rpm-sequoia as a more feature complete library. Runtime-depend on rpm-sequoia-crypto-policy. (From OE-Core rev: d8b01b436d37f4deb2de5d234e8f04c957719ca3) Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm-sequoia-crypto-policy: New recipeZoltán Böszörményi2025-02-181-0/+1
| | | | | | | | | This ships a crypto policy file for rpm-sequoia. (From OE-Core rev: 8e499cefab6bfb40b40ae3eb811ca3eb51a7d4bc) Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-fitimage.bbclass: introduce FIT_UBOOT_ENVAdrian Freihofer2025-02-111-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce a new variable FIT_UBOOT_ENV, which allows to add a u-boot script as a text file to the fitImage. Such a script can be sourced from the u-boot shell, as documented here: https://docs.u-boot.org/en/latest/usage/cmd/source.html#fit-image The kernel-fitimage.bbclass also evaluates the existing UBOOT_ENV variable and adds the corresponding script to the fitImage. However, the UBOOT_ENV variable is also used to install the script as an old u-boot image, usually named boot.scr into the /boot directory of the target device. These are different use cases which should be handled independently. Appending the script to the u-boot recipe and then hand it over to the kernel recipe via the staged /boot directory leads to complicated task dependencies. Decoupling the two use cases will also allow to simplify the implementation by dropping the evaluation of the UBOOT_ENV variable in the kernel-fitimage.bbclass. But this commit is supposed to be backward compatible. (From OE-Core rev: 269605ed053fd8dc7bcbcc04a46c308188115f66) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: Add description for IMAGE_ROOTFS_MAXSIZE variableWeisser, Pascal.ext2025-02-101-0/+1
| | | | | | | (From OE-Core rev: 8c4281b66ad87f8f951314252eb6ab8fc711212b) Signed-off-by: Weisser, Pascal <pascal.weisser.ext@karlstorz.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade to 2.41 releaseKhem Raj2025-02-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | License-Update: Added license for e_gammaf_r.c [1] added url of CORE-MATH project [2] * Testing support with different compilers (series) * Remove XXX math functions from installed math.h (patch) * Remove "%n" from assert (commit) * Improve executable stack handling * Compile glibc tests with Clang (series 1, series 2) * asprintf should write NULL on failure * Revert TCB layout changes * Fix ld.so crashes with golang test suite * Fixes after GET_ADDR_ARGS removal * Extend Rseq Support, plus x32 fixup * sh4: ensure FPSCR.PR==0 when executing FRCHG [BZ #27543] * affinity-inheritance test: overallocate CPU sets * rseq-related aarch64 test failures * arc4random test failure under load * benchtests: Add dummy in put files cospi, cospif, sinpi, sinpif, tanpi, tanpif * pthread condvar missing signal, bug 25847 * aarch64: Add support for Guarded Control Stack extension * testsuite: Make stdio-common/tst-printf-format-*-mem UNSUPPORTED if the mtrace output does not exist Further Release Notes [3] [4] [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=2843e78b30da0aa743fdfb0ac61435c925182c04 [2] https://sourceware.org/git/?p=glibc.git;a=commit;h=d421d36582281a62e05f96a1bfb085db9d85f40b [3] https://sourceware.org/glibc/wiki/Release/2.41 [4] https://sourceware.org/pipermail/libc-announce/2025/000045.html (From OE-Core rev: 73b34ff50c8e5b05eca8f9a236bd1b155bd14324) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest-packagelists: remove valgrindRandy MacLeod2025-02-051-7/+4
| | | | | | | | | | The valgrind-3.24 and glibc-2.41 update result in lots of valgrind ptests failing. Remove all valgrind ptests until that can be fixed. (From OE-Core rev: 98d5a6a68e9e7df671e40480faed48ab2114dd7f) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuriscv: Enable Sv39 memory address scheme by defaultYash Shinde2025-02-051-0/+1
| | | | | | | | | | | | | | | | | | | | Currently, GCC Asan supports only Sv39 on RISC-V 64 due to custom allocator configurations optimized for large allocations. These configurations are incompatible with larger address spaces like Sv48/Sv57. This fix enables RISC-V 64 configuration for RVA22S64 profile(which has sv39 mode and other extensions) by default when running `runqemu nographic`, eliminating the need for manual configuration via command line flags (`qemuparams="-cpu rv64, sv39=true"`). Fixes [YOCTO #15691] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15691 Reference: https://github.com/qemu/qemu/commit/af651969eb23ecf018bcaa8e0761b58425de550c https://git.openembedded.org/openembedded-core/commit/?id=4b4450ff695ef73bf7a2437e142d2e0730d6a547 (From OE-Core rev: 5e749a2576698e390392b5d522a2dc5fdc9556cd) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.44 releaseKhem Raj2025-02-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Drop the CVE-2024-53589 patch, its included in 2.44 * Package newly rename gp-* to gprofng-* binaries and remove old gp-* symlinks * Gold linker is now deprecated and will be removed in future release its already deleted in tarball releases * Support for the Nios II target has been removed. * Assembler: - Support for new architecture extensions for AArch64, Risc-V and x86. * Linker: The default maximum page size was changed from 16KiB to 64KiB for LoongArch. This now supports mixed LTO and non-LTO object files in relocatable output. The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD. The --build-id= option now accepts an argument of "xx" which enables the use of the xxhash library. This produces a 128-bit hash and is 2-4x faster than md5 or sha1. The ELF linker option --package-metadata supports percent-encoded and %[string] encoded JSON payloads. * Disassembler: The RISC-V disassembler now supports -M,max option like QEMU to dump instruction without checking architecture support as usual. * GprofNG: Support added for hardware event counters for Neoverse-N1, Ampere-1, and Appliedmicro processors. Detailed release notes [1] [1] https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html (From OE-Core rev: df3c43e69542939a4bec3893f1e927edf2ad7179) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nss-mdns: Rename recipe to avahi-libnss-mdnsAlex Kiernan2025-02-052-2/+2
| | | | | | | | | | | meta-networking has Apple's mDNSResponder which also delivers libnss-mdns nsswitch plugin. Rename this recipe to avahi-libss-mdns and add an RPROVIDE so that either than be chosen. (From OE-Core rev: f9d10d6ac4b2a081d110ab58e7137aedddd960cb) Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* licenses: Map SGIv1 to SGI-OpenGLBastian Germann2025-02-051-1/+1
| | | | | | | | | | SGI-1 is not a SPDX license identifier. However, the SGI-1 license has the same license text as SGI-OpenGL. Map the old SGIv1 name to SGI-OpenGL. (From OE-Core rev: e97a9c3c86a8fe27a26ad69174ba50e5228846e5) Signed-off-by: Bastian Germann <bage@debian.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/meta-selftest: Fix variable assignment whitespaceRichard Purdie2025-02-011-1/+1
| | | | | | | | | | Recipes are much more readable with whitespace around the assignment operators. Fix various assignments in OE-Core to show this is definitely the preferred formatting. (From OE-Core rev: 30ea609d3357fb3de911f2f6a5e6856c151b976a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: Upgrade 15.2 -> 16.1Yash Shinde2025-01-272-2/+2
| | | | | | | | | | | | | | | | | * Drop 0001-Fix-Wenum-constexpr-conversion-in-enum-flags.h.patch, its already applied to gdb 16.1 Detailed release notes: https://sourceware.org/pipermail/gdb-announce/2025/000143.html https://sourceware.org/gdb/news/ https://lwn.net/Articles/1005562/ https://www.sourceware.org/gdb/download/ANNOUNCEMENT (From OE-Core rev: 31a536ed8c4d03db250766fe701126dd14d084c0) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Handle empty BB_CURRENT_MCRichard Purdie2025-01-251-1/+1
| | | | | | | | | | | | | | | | | | | Bitbake is about to change the default value of this from "default" to "". The original reason for this was to make this kind of include file usage easier. Instead we were going to complicate bitbake code having to map one value into the other. Instead, stop using "default" and put a slightly horrible bit of code in bitbake.conf as an alternative. This means a "default.conf" in the multiconfig directory will stop working but this was never something anyone was expected to use. The eSDK code also needs updating for this change. (From OE-Core rev: ff469ab2e865063bbc529031bbfd76cba5040073) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: kernel-fitimage: Fix dependency loop if UBOOT_SIGN_ENABLE and ↵Marek Vasut2025-01-221-0/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | UBOOT_ENV enabled In case both UBOOT_SIGN_ENABLE and UBOOT_ENV are enabled and kernel-fitimage.bbclass is in use to generate signed kernel fitImage, there is a circular dependency between uboot-sign and kernel-fitimage bbclasses . The loop looks like this: kernel-fitimage.bbclass: - do_populate_sysroot depends on do_assemble_fitimage - do_assemble_fitimage depends on virtual/bootloader:do_populate_sysroot - virtual/bootloader:do_populate_sysroot depends on virtual/bootloader:do_install => The virtual/bootloader:do_install installs and the virtual/bootloader:do_populate_sysroot places into sysroot an U-Boot environment script embedded into kernel fitImage during do_assemble_fitimage run . uboot-sign.bbclass: - DEPENDS on KERNEL_PN, which is really virtual/kernel. More accurately - do_deploy depends on do_uboot_assemble_fitimage - do_install depends on do_uboot_assemble_fitimage - do_uboot_assemble_fitimage depends on virtual/kernel:do_populate_sysroot => do_install depends on virtual/kernel:do_populate_sysroot => virtual/bootloader:do_install depends on virtual/kernel:do_populate_sysroot virtual/kernel:do_populate_sysroot depends on virtual/bootloader:do_install Attempt to resolve the loop. Pull fitimage configuration options into separate new configuration file image-fitimage.conf so these configuration options can be shared by both uboot-sign.bbclass and kernel-fitimage.bbclass, and make use of mkimage -f auto-conf / mkimage -f auto option to insert /signature node key-* subnode into U-Boot control DT without depending on the layout of kernel fitImage itself. This is perfectly valid to do, because the U-Boot /signature node key-* subnodes 'required' property can contain either of two values, 'conf' or 'image' to authenticate either selected configuration or all of images when booting the fitImage. For details of the U-Boot fitImage signing process, see: https://docs.u-boot.org/en/latest/usage/fit/signature.html For details of mkimage -f auto-conf and -f auto, see: https://manpages.debian.org/experimental/u-boot-tools/mkimage.1.en.html#EXAMPLES Fixes: 5e12dc911d0c ("u-boot: Rework signing to remove interdependencies") Reviewed-by: Adrian Freihofer <adrian.freihofer@siemens.com> (From OE-Core rev: 259bfa86f384206f0d0a96a5b84887186c5f689e) Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base: Switch virtual/cross-XXX to be under recipe specific providersRichard Purdie2025-01-211-0/+1
| | | | | | | | | | | | | | | Currently, providers are set on a global config basis. This change allows for a select set of providers to be configured using BB_RECIPE_VIRTUAL_PROVIDERS on a per recipe basis. This would allow for the selection of virtual/cross-cc as gcc or clang for example. The PROVIDERS are removed from the recipes so that if a version of the dependency accidentally slips through, the build will fail and the user can correct the issue. (From OE-Core rev: 6eeab1a5d7f23917b94c130e417d59afb757b546) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/recipes: Switch virtual/XXX-gcc to virtual/cross-cc (and c++/binutils)Richard Purdie2025-01-212-10/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea of the base class dependency is to say "yes, I need a C cross compiler" and this was never meant to be gcc specific. Looking at the codebase, whilst we code triplets into this, it does overcomplicate things as there are only ever limited, "target", "sdk" and the class extended versions like mutlilib. After much thought, we can simplify this to virtual/cross-cc and virtual/nativesdk-cross-cc. This lets us remove the "gcc" specific element as well as removing the over complicated triplet usage. At the same time, change the much less widely used "g++" variant to "c++" for similar reasons and remove the triplet from virtual/XXX-binutils too. Backwards compatibility mappings could be left but are just going to confuse things in future so we'll just require users to update. This simplification, whilst disruptive for any toolchain focused layers, will make improved toolchain selection in the future much easier. Since we no longer have overlapping variables, some code for that can just be removed. The class extension code does need to start remapping some variables but not the crosssdk target recipe names. This patch is in two pieces, this one handles the renaming with the functional changes separate in a second for easier review even if this breaks bisection. (From OE-Core rev: 4ccc3bc8266c327bcc18c9a3faf7536210dfb9f0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.80.1->1.81.0Deepesh Varatharajan2025-01-141-1/+1
| | | | | | | | | | | | | | | | | | https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html Drop the following backported patches which is addressed with rust v1.81.0 upgrade. 0001-cargo-do-not-write-host-information-into-compilation.patch https://github.com/rust-lang/cargo/commit/2db0bab16139d094f689587b73539aae386a1919 hardcodepaths.patch https://github.com/rust-lang/rust/commit/28503d69ac204ff208d115aea30dc09d6fca8728 (From OE-Core rev: 611ec9ffbac974f472a828277ba7f3e344e99ca3) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib.conf: overwrite conf files for debsBenjamin Bara2025-01-111-0/+1
| | | | | | | | | Similar to OPKG, overwrite conf files for APT (deb files). (From OE-Core rev: b1d29b8b05ea7ebdb04f53afc0003bc04d8e71ec) Signed-off-by: Benjamin Bara <benjamin.bara@skidata.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu/machine: rename QEMU_EXTRAOPTIONS for consistencyRoss Burton2025-01-1112-38/+38
| | | | | | | | | | | | | | | | | The per-tune qemu options variable is QEMU_EXTRAOPTIONS_${TUNE_PKGARCH}, but this doesn't follow the pattern of all of the other tune-specific variables in the machine configuration which is VARIABLE:tune-[name]. Rename QEMU_EXTRAOPTIONS_${TUNE_PKGARCH} to QEMU_EXTRAOPTIONS:tune-${TUNE_PKGARCH} for consistency. Note that this will mean that BSPs need to update any assignments of this variable. (From OE-Core rev: 7f981d074442b901f7e64dbdb9db851ff31c3733) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/qemu: move QEMU_EXTRAOPTIONS for PPC to the relevant tunesRoss Burton2025-01-116-0/+8
| | | | | | | | | | Every other architecture has the QEMU_EXTRAOPTIONS assignments in the tune files, so move the PPC ones too. (From OE-Core rev: ba05251c89d8cc243e861886124573c83197e949) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* blktool: remove the recipeAlexander Kanavin2025-01-102-2/+0
| | | | | | | | | | It was created in 2004 as an alternative to hdparm and never updated since (while hdparm remains in active development). (From OE-Core rev: 54c1243a259a2f6407c0202d03414fc5272b2d90) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/distro/defaultsetup: Use include_all for maintainers.incRichard Purdie2025-01-081-1/+1
| | | | | | | | | | | Being able to set maintainers is really a "per layer" configuraiton item. Use include_all so that such maintainer information would be added for all configured layers, if the layer chooses to have such information in a conf/distro/include/maintainers.inc file in a given layer. (From OE-Core rev: d6b9dc4629642a4bf0d8f34a90bd8e3291c87501) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop obsolete and misleading commentRichard Purdie2025-01-081-2/+0
| | | | | | | | | | | "packaged staging" is obsolete and now we have sstate. Multimachine is just the norm now, I doubt people remember how things used to be! Drop the comment as it is misleading and obsolete. (From OE-Core rev: 808d2a526e3dd6d77c524d8faa0af3e78cf0bed6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add libstdc++-native to ASSUME_PROVIDEDRichard Purdie2025-01-081-0/+1
| | | | | | | | | Fixing native class extension code highlighted this was missing, we do assume the system has a working libstdc++ compiler/runtime. (From OE-Core rev: a9ae7001adeecf420d9a95654ce27d7e7b8f82a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add bash-completion-native to ASSUME_PROVIDEDRichard Purdie2025-01-081-0/+1
| | | | | | | | | | | | With some native dependency handling fixes under discussion, bash-completiion-native makes it into the dependency chain. Add this to ASSUME_PROVIDED since we don't want to build it rather than trying to remove all references in the native case (it comes from glib-2.0-native). (From OE-Core rev: 401706ed6d51917d76726098a767932970990805) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/bitbake.conf: move addfragments to just after the local.conf includeAlexander Kanavin2025-01-031-3/+5
| | | | | | | | | | | | | There was a report that the existing addfragments statement comes in too late, specifically after the DISTRO/MACHINE includes have already been handled. The goal for fragments content is to behave exactly like the settings in local.conf would and so we need to handle the fragments just after that file. (From OE-Core rev: e820fa96d078478ea3510164373989090e8c9419) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Upgrade 9.1.1 -> 9.2.0Richard Purdie2024-12-171-1/+1
| | | | | | | | Drop two patches merged upstream. (From OE-Core rev: 540ba2ce2f6d138b386d0d7545c197fd7f54edc8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add an addfragments directive for oe-core and dependent layersAlexander Kanavin2024-12-131-0/+3
| | | | | | | | | | | | Please see the patch to bitbake for syntax and implementation details. The path prefix to fragments is in its own variable so it doesn't have to be hardcoded into tools. (From OE-Core rev: 5bdbabd7b5d244a44c33065b04dd76dad76888a8) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add self for meson, python3 recipesTrevor Gamblin2024-12-121-4/+4
| | | | | | | | | | | | | | | | The following recipes recently had their maintainership given up, so list myself as maintainer for them: - meson - python3-markdown - python3-smartypants - python3-typogrify (From OE-Core rev: caaa2d4345e9d9e9f1a313c5f4f1ed4e3539fea3) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: Update maintainer for pseudo and rpmRobert Yang2024-12-121-2/+2
| | | | | | | | (From OE-Core rev: cc9a55d464503ef1275daf4e2121741df8a4d750) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-c: convert to target recipeAlexander Kanavin2024-12-121-1/+1
| | | | | | | | | | | | | | | This was prompted by sstatetests.SStateHashSameSigs2.test_sstate_allarch_samesigs where adwaita-icon-theme would fail due to new librsvg introducing cargo-c-native into dependency path. Rather than look into why is that, I simply converted the recipe into the standard 'target + BBCLASSEXTEND' approach. (From OE-Core rev: 80a2673a3081e623f30f25cc773ac9217e717958) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-iniparse: remove recipeGuðni Már Gilbert2024-12-092-2/+0
| | | | | | | | | | | | There are no consumers of this recipe in openembedded-core or in meta-openembedded. The last consumer was dnf: https://git.openembedded.org/openembedded-core/commit/?id=05220b4907ab654e829d97ab68d48f76330937dd (From OE-Core rev: 5915e70469fa53600dd8926ddafcb5459df1a32c) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: unassign myself (don't panic!)Alexander Kanavin2024-12-051-95/+95
| | | | | | | | | | | | | | For a very long time my focus hasn't been these recipes in particular; rather I'm trying to ensure oe-core as a whole doesn't fall too far behind upstream releases. To better reflect this reality, I wish to be no longer listed for any specific recipes. (From OE-Core rev: b420b575fef9111a264a9ecc3b34a341ee604d97) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: define keymaps virtual runtime providerPeter Marko2024-11-282-1/+1
| | | | | | | | | | | | VIRTUAL-RUNTIME_keymaps is defined in busybox init manager and also in some package groups. Defining distro features in recipes is wrong. Also this is not directly related to init manager. So move all these definitions to default-providers.inc (From OE-Core rev: 00f667bb5007a372950a137bf9e8b0e62f44f7d6) Signed-off-by: Peter Marko <peter.marko@siemens.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-07 21:45:34 +0000