summaryrefslogtreecommitdiffstats
path: root/meta/conf/distro/include
Commit message (Collapse)AuthorAgeFilesLines
...
* rust: Upgrade 1.83.0->1.84.1Deepesh Varatharajan2025-03-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | 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->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 <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scdoc: Import from meta-waylandAlex Kiernan2025-03-171-0/+1
| | | | | | | | | scdoc is a simple man page generator for POSIX systems written in C99. (From OE-Core rev: 00c9683ae5ca5dd2d4490caa7a408a1a04a60f13) Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: eliminate needless linux-libc-headers version defaultsRandy MacLeod2025-03-171-3/+0
| | | | | | | | | | | | | | | | | Manually setting the preferred version is not required or generally a good idea as stated in: meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc # You're probably looking here thinking you need to create some new copy # of linux-libc-headers since you have your own custom kernel. To put # this simply, you DO NOT. so remove that for linux-libc-headers. (From OE-Core rev: 72eca56ba754079733da49403b59205a44b24709) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* 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>
* 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-051-11/+2
| | | | | | | | | | | | 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* init-manager: define dev_manager for all init managersPeter Marko2024-11-282-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Currently VIRTUAL-RUNTIME_dev_manager is defined by some init managers with "??=" and in packagegroup-core-boot with "?=". This means that this variable is different in this package group and in all other the recipes. This was discovered when trying to use new feature INIT_MANAGER when migrating to scarthgap and using systemd distro. After deleting all VIRTUAL_RUNTIME providers defined in init-manager-systemd udev was installed additionally via packagegroup-core-boot. Having a distro settings overriden in single recipe is wrong and needs to be corrected. Therefore let's define the setting in all init managers and remove it from packagegroup-core-boot. core-image-tiny-initramfs has a dilemma - use busybox-mdev even if distro does not enable it in busybox recipe to keep the image tiny, or rather not install it even if distro enables it in busybox. This patch chooses the first option. (From OE-Core rev: 89e2652ac83f2602d6dd60623a225b88dc67d288) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-isodate: move to meta-pythonGuðni Már Gilbert2024-11-281-1/+0
| | | | | | | | | python3-rdflib was the last consumer of this recipe in oe-core. (From OE-Core rev: 72cc499429b0869385223ba21fe03849c6145b89) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdisplay-info: add recipeHiago De Franco2024-11-271-0/+1
| | | | | | | | | | | | | | | | | | libdisplay-info is a EDID and DisplayID library. Goals: - Provide a set of high-level, easy-to-use, opinionated functions as well as low-level functions to access detailed information. - Simplicity and correctness over performance and resource usage. - Well-tested and fuzzed. Since commit a16598b038b2 ("backend-drm: make libdisplay-info mandatory") from Weston, this library is now mandatory in order to build weston 14.0.1 and newer. (From OE-Core rev: aa3fe5a5c00085f5455a66c1033f4124e76239ec) Signed-off-by: Hiago De Franco <hiago.franco@toradex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* hwdata: add recipe from meta-openembeddedHiago De Franco2024-11-271-0/+1
| | | | | | | | | | | | | | | | | Move hwdata recipe from meta-openembedded to openembedded-core. libdisplay-info is now a requirement for Weston, since commit a16598b038b2 ("backend-drm: make libdisplay-info mandatory"). However, in order to build libdisplay-info, hwdata is required. Since Weston is built inside openembedded-core, move hwdata in order to be able to upgrade Weston, so oe-core has no dependency on meta-oe. hwdata contains various hardware identification and configuration data. (From OE-Core rev: 3e5d5ba74beace1669ff04a7b0334aaa2693bdb6) Signed-off-by: Hiago De Franco <hiago.franco@toradex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* liburi-perl: move to meta-perlAlexander Kanavin2024-11-272-2/+0
| | | | | | | | | | | liburi-perl was added in 2010 to support lsb testing, never had any other consumers in core, and since 2019 lsb testing is gone as well: https://git.yoctoproject.org/poky/commit/?h=master-next&id=bac4bc9aa6a1f2fcf2ce9644925615185cc8e847 (From OE-Core rev: 945e77e789c93ed889ceca75d61ab7cfd39fb1b8) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v6.12Bruce Ashfield2024-11-221-1/+1
| | | | | | | | | | Updating linux-libc-headers to the 6.12 LTS release, we drop 6.10 and make 6.12 the default. (From OE-Core rev: ac76d281e28cf0cb42dd76869572fa01716198ca) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu/testimage: Ensure GNU tar is in test imagesRichard Purdie2024-11-211-0/+2
| | | | | | | | | | | | | | | | We've seen cases where a ptest (strace) has a 43GB sparse file in the test directory. busybox tar doesn't work well with this. The resulting 1.4GB archive takes hours to extract too. Ensure tar is added to our full images and use the sparse option to collect files for debugging. This stops crazy build hangs. Since tar is GPLv3, we have to exclude it from that test code. We don't boot any of those images so the debug collection code is safe there, at least for now. (From OE-Core rev: fefeb919696b6ac76f0997acfb0f612203ef7f1b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.79.0->1.80.0Harish Sadineni2024-11-181-1/+1
| | | | | | | | | | | | | | | | | Update the patch files with rust v1.80.0. The patch repro-issue-fix-with-cc-crate-hashmap.patch addresses the rust reprouciblity issue by correcting the way hash values are generated for different build paths. https://blog.rust-lang.org/2024/07/25/Rust-1.80.0.html (From OE-Core rev: d68449da0df795abe3233383a82d0b6b7908d736) Signed-off-by: Sunil Dora <SunilKumar.Dora@windriver.com> Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers.conf: add virtual-x-terminal-emulatorRoss Burton2024-11-141-0/+2
| | | | | | | | | | | | | We have multiple recipes in core that RPROVIDE virtual-x-terminal-emulator, so we should pick one to be the default for deterministic builds. Pick rxvt, as it's the lightest. Sato can depend on matchbox-terminal explicitly and rxvt will not be added. (From OE-Core rev: 0c362390127fa30f6932558ebcd9cbe1e21e8467) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl8: re-add tcl 8 to support building expectAlexander Kanavin2024-11-122-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | I'd be happy to remove expect from core as it has been unmaintained for years, but sadly gcc/binutils test suites are basically written in it (via dejagnu), and ltp makes use of it as well. I attempted porting expect to tcl 9, but it's a tcl extension and makes extensive use of features that have been deprecated in tcl 8 and removed in tcl 9, and even pokes into tcl internals. At some point hopefully the GNU toolchain upstreams are going to notice; for now we'll carry tcl (latest) and tcl8 recipes. tcl and tcl8 packages can be co-installed, the latter is adjusted to contain tclsh8. tcl-dev and tcl8-dev packages can also be co-installed, a few files in tcl8-dev are renamed to avoid clashes with tcl-dev (tcl.pc -> tcl8.pc, and similar for tclConfig.sh and tclooConfig.sh). (From OE-Core rev: 8ec7bfc6644aff011545dfb0f5a415e79d7b0844) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* time64: Fix incorrect recipe override syntaxRichard Purdie2024-10-251-1/+1
| | | | | | | | The original commit incorrectly missed off the pn- override prefix, fix it. (From OE-Core rev: 766ebeec6fa56305606df3dcf901053dd58c1a95) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* time64.inc: Exclude pseudo from the 32bit-time warningsRichard Purdie2024-10-241-0/+4
| | | | | | | | | pseudo has to wrap all glibc calls including the 32 bit ones so this warning is a false positive. (From OE-Core rev: 13f8b50f055be219aed50c62c5f7552c4c2f18f2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Upgrade 9.0.1 -> 9.1.0Richard Purdie2024-10-221-1/+1
| | | | | | | | Drop the gnutls patch since something equivalent was merged upsteam. (From OE-Core rev: 3e1b5805906dc3b2f7c79d26224a7a732123af97) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers: Switch U-Boot to FabioMarek Vasut2024-10-151-2/+2
| | | | | | | | | | | Fabio has been keeping the U-Boot recipe up to date for a long time in a timely manner, doing a great job there, update the maintainers file. (From OE-Core rev: ba8d7c7d066ae4923a7494775077f23939183d21) Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* makedumpfile: import 1.7.5 from meta-openembeddedEtienne Cordonnier2024-10-151-0/+1
| | | | | | | | | | | | The kdump script from kexec-tools does not work without makedumpfile (see https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/kexec/kexec-tools/kdump#n14 ). Thus, let's import makedumpfile from meta-openembedded/meta-oe/recipes-kernel/makedumpfile and make kexec-tools RDEPENDS on makedumpfile. makedumpfile is the utility which reads /proc/vmcore after a kernel panic and creates a kdump file under /var/crash/. (From OE-Core rev: 8534e6427622ec76e100b7d10ee11d180cf5980a) Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* barebox-tools: add initial barebox tools supportMarco Felsch2024-10-111-0/+1
| | | | | | | | | | | | | | | | Add initial support to build the barebox tools for the host and the target. Some of the tools are generic barebox utilities (like 'bareboximd' for image meta data inspection or 'bareboxenv' for accessing the barebox environment) some are SoC family-specific specific utilities (like 'imx-usb-loader' or 'omap3-usb-loader'). (From OE-Core rev: cb3de34a28cde3f9ebd52ba842da9f91c6f0fa66) Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* barebox: add initial supportMarco Felsch2024-10-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the support for the barebox bootloader to oe-core. The recipe is inspired by meta-ptx [1] but is a major rework of the one found there. Barebox comes with a wide range of supported architectures and follows the concepts of Linux in various aspects like the driver model, the shell, or the virtual file system. This not only eases porting Linux drivers but also makes barebox a developer-friendly and feature-rich bootloader alternative [2]. For barebox (like for the kernel or other bootloaders) it is quite likely that people will not just build the original recipe but need to adapt it, point to custom repositories, apply patch stacks, COMPATIBLE_MACHINE etc. They may also choose to have different recipe names for different variants. Having only a single .bb file and requiring to copy or .bbappend it is inconvenient and results in unnecessary code duplication. Therefore, the base support for building barebox is encapsulated in barebox.bbclass (like kernel.bbclass for the kernel). Adds barebox to maintainers.inc but excludes it from the maintainers check since with the current check mechanism barebox would be skipped (and making the check fail) due to not being the PREFERRED_PROVIDER for virtual/bootloader. [1] https://github.com/pengutronix/meta-ptx/tree/master/recipes-bsp/barebox [2] https://www.barebox.org/demo/?graphic=0 (From OE-Core rev: 5c69f5626278a6e9756188a5771b18075380f52d) Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>