summaryrefslogtreecommitdiffstats
path: root/meta/conf/distro/include
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* gdb: Upgrade 15.1 -> 15.2Deepthi Hemraj2024-10-081-1/+1
| | | | | | | | | | | | | | | | | | | GDB 15.2 brings the following fixes: * PR gdb/31727 (-exec-next fails in mingw (infrun.c:2794: internal-error: resume_1: Assertion `pc_in_thread_step_range (pc, tp)' failed)) * PR c++/31900 (libstdc++-prettyprinters/debug.cc print redirected fails since gdb-14-branchpoint-2123-g4e417d7bb1c) * PR python/31946 (sys.exit from Python no longer exits the GDB process) * PR record/31971 (Loading a saved record file asserts if we try to execute the inferior) * PR gdb/32005 (frv_current_sos doesn't set solib::lm_info) * PR exp/32015 (GDB crashes while printing large D array) * PR gdb/32025 (Fatal error when the disassemble command is interrupted with SIGINT) * PR gdb/32143 ([15 Regression] arch/amd64.c:71: internal-error: amd64_create_target_description: Assertion `!is_x32' failed) * PR symtab/32158 ([gdb/symtab] enum class enumerator has incorrect parent in cooked index) * PR symtab/32160 ([gdb/symtab] Parent map: die parent or scope parent?) (From OE-Core rev: 76567e7a0e1d133b5878a0254a9dcc87b3a15bc1) Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars: Have KERNEL_CONSOLE reference SERIAL_CONSOLESJon Mason2024-10-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | Currently, KERNEL_CONSOLE has a default value of "ttyS0". However, Arm machines and those using virtio serial prefer to use "ttyAMA0" or "hvc0" (or something else). These are usually defined by the machine config file as SERIAL_CONSOLES, which has one or more entries. Take the first one of those instead of ttyS0, but default back to ttyS0 if nothing is set. Also, use this variable in the efi wic file instead of "ttyS0". Of note, this changes the default speed of the default kernel console from undefined (9600) to 115200. This allows for users of the mkefidisk.wks to work as before but any users of this variable could see changed behavior and would now need to define this as: KERNEL_CONSOLE ?= "ttyS0,9600" This includes revisions suggested by Quentin Schulz and Ross Burton. (From OE-Core rev: da42fc9ad55d1d60a04e38ff94c965f711f60cd6) Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add python3-pefileMikko Rapeli2024-10-011-0/+1
| | | | | | | | | | | Recipe moved from meta-oe to oe-core and Khem Raj <raj.khem@gmail.com> agreed to continue as maintainer. (From OE-Core rev: ea18f44d81e95cd14ebfbc24c6089b556486aab3) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pefile: add recipe from meta-openembeddedMikko Rapeli2024-10-011-0/+1
| | | | | | | | | | It is needed by systemd ukify tool and uki.bbclass to generate UEFI boot binaries. Added to fast list in ptest-packagelists.inc. (From OE-Core rev: 4069c485046fe6d008dd0c48269f29d92146d923) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security-flags: Re-enable pie for power pcBenjamin Grossschartner2024-09-201-6/+0
| | | | | | | | | | | pie now works with gcc on powerpc, see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81170 (From OE-Core rev: f9ef9af3874bf435e2f92fdf1ebe852b099fa7b5) Signed-off-by: Benjamin Grossschartner <benjamin.grossschartner@urbanandmainlines.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.78.0->1.79.0Yash Shinde2024-08-291-1/+1
| | | | | | | | | | | | | | | | Update the patch files with rust v1.79.0. Drop the following backported patch which is merged with rust v1.79 upgrade. - cross-targets-backport.patch https://blog.rust-lang.org/2024/06/13/Rust-1.79.0.html (From OE-Core rev: 0e20d8e0a292f720c9ed419547d8f6d738c5d4d8) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-inclusions: encode CPEs of affected packagesMarta Rybczynska2024-08-201-12/+12
| | | | | | | | | | | Add the new cpe:vendor:product tagging to entries in cve-extra-inclusions, using product/vendor combinations that are already present in OE-core (usually there is no specific vendor). (From OE-Core rev: e1bf43561093b3b9215cde9e9f7d80b4ffcdc64e) Signed-off-by: Marta Rybczynska <marta.rybczynska@syslinbit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.77.2->1.78.0Yash Shinde2024-08-201-1/+1
| | | | | | | | | | | | | | | | * Drop the following backported patches which are merged with rust v1.78 upgrade. - 0001-Revert-Map-source-absolute-paths-to-OUT_DIR-as-relat.patch - repro-issue-fix-with-v175.patch - deadcode-backport.patch https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html (From OE-Core rev: a3fb378afcc1fb01e9813fe902dbd6090ded75d7) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.76.0->1.77.0Yash Shinde2024-08-091-1/+1
| | | | | | | | | | | | * Drop backported patch 0001-Handle-vendored-sources-when-remapping-paths.patch as it's merged with rust v1.77.0. https://blog.rust-lang.org/2024/03/21/Rust-1.77.0.html (From OE-Core rev: 8b6b224fc116150c0af658473eecd05b742de7b1) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.75.0->1.76.0Yash Shinde2024-08-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | * Drop "--doc" option for rust oe-selftest since it is not supported on bootstrap builds for cross-targets. * Drop the following backported patches which are merged with rust v1.76 upgrade. - custom-target-cfg.patch - rustc-bootstrap.patch - rv32-missing-syscalls.patch - target-build-value.patch https://blog.rust-lang.org/2024/02/08/Rust-1.76.0.html * Drop 'rust-rustdoc' and 'rust-dbg' from 'exclude_packages' list to check for rust reproducibility. (From OE-Core rev: 71d17ed3c7be029fc68e9dd3f5d6c4aa72ef861a) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to GCC 14.2Khem Raj2024-08-081-1/+1
| | | | | | | | | | | | This is first bugfix release in GCC14 release series 100+ bugfixes [1] [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=14.2 (From OE-Core rev: 32b39de6a23f1e9ae5786d63f4c5849301eddbda) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-tomli: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | | Most packages use tomllib and fall back to tomli. The last user in core was python3-setuptools-scm, removed in 5c8a0a2. (From OE-Core rev: 0dc792a62df6b6ceec4c897c41d13238e829af61) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-toml: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | | There are no potential users of this recipe now that importlib_metadata has been removed, and importlib_metadata used tomllib anyway. (From OE-Core rev: 865e731392e1581b081e21287ebdae0b0f483aca) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-importlib-metadata: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | | | | This package is a backport of the importlib.metadata standard library package, so shouldn't really be needed since we have Python 3.12. The last user in core was pytest, removed in 0aee9aa. (From OE-Core rev: 686bae9aff26410eaa1ab591bca91c00c4b029ef) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pytest-runner: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | | | This is a deprecated package so rarely used now. The last user in core was python3-chardet, removed in 55b49e9. (From OE-Core rev: bb00747abc1312efb1059dec6d585488d6edbdee) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-py: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | The last user in core was pytest, removed in 0aee9a. (From OE-Core rev: 6c0f07ba43646aa7987dfc3de8871b55f875fa07) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-rfc3986-validator: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | | | | The only user of this recipe in core is python3-jsonschema, but only if you select the non-default 'nongpl' PACKAGECONFIG. Move to meta-python so it's there if needed. (From OE-Core rev: 41ecbbe06f3d747cb68789817e19b600d672d9ea) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pathlib2: remove recipe (moved to meta-python)Ross Burton2024-08-071-1/+0
| | | | | | | | | | | | This recipe is a backport of pathlib intended for older releases of Python but as we have a modern release of Python it shouldn't be needed. There are no users in oe-core, so move to meta-python. (From OE-Core rev: 4857b287a86ad0c2afed4bdfabe18c545bc9291b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.43 releaseKhem Raj2024-08-061-1/+1
| | | | | | | | | | | Detailed changelog [1] [1] https://sourceware.org/pipermail/binutils/2024-January/132213.html (From OE-Core rev: 7e7afecc532a451b0ca9f34195a287c6472063c0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-libarchive-c: add ptestCorentin Lévy2024-08-051-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | test added to the fast-list result of ptest-runner: Testsuite summary TOTAL: 36 PASS: 36 SKIP: 0 XFAIL: 0 FAIL: 0 XPASS: 0 ERROR: 0 DURATION: 11 END: /usr/lib/python3-libarchive-c/ptest 2024-08-01T11:44 STOP: ptest-runner TOTAL: 1 FAIL: 0 (From OE-Core rev: 2019edfc5a6fd252329347a6230a2e39603b932b) Signed-off-by: Corentin Lévy <corentin.levy@smile.fr> Reviewed-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v6.10Bruce Ashfield2024-08-031-1/+1
| | | | | | | | | | 6.10 will be the reference kernel version for the fall release, so we bump our libc-headers to match. (From OE-Core rev: 3f852c2c958c80c652e902ab0532cefdc82e6549) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* time64.inc: Simplify GLIBC_64BIT_TIME_FLAGS usageTom Hochstein2024-07-261-1/+2
| | | | | | | | | | | | | | | | | | | | | | | The implementation uses the append operator to include GLIBC_64BIT_TIME_FLAGS in TARGET_CC_ARCH, but it places the space in the GLIBC_64BIT_TIME_FLAGS assignment in order to avoid a 'spurious space' when the value is empty. 68b50d3 time64: Remove leading whitespace from GLIBC_64BIT_TIME_FLAGS The problem with this is it requires anyone wishing to assign a value to GLIBC_64BIT_TIME_FLAGS to add the leading space, otherwise this is the error: cc1: error: '-Werror=format-security-D_TIME_BITS=64': no option '-Wformat-security-D_TIME_BITS=64' Add a new constant variable to capture the value needed for the 32-bit special case, including the space. (From OE-Core rev: e8177827f92e71c80c5b63453d8bbd1defbe1fbc) Signed-off-by: Tom Hochstein <tom.hochstein@oss.nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-08-15 04:00:17 +0000