summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
* python3-license-expression: fix ptest installationRoss Burton2025-02-181-3/+4
| | | | | | | | | | | | | This recipe was overriding do_install_ptest which is provided by the ptest-python-pytest class, so there was no tests or run-ptest installed. Use an append override, and minimise the installed files: use a symlink so that scancode-licensedb-index.json is found and install setup.cfg. (From OE-Core rev: 164876d33af9edaac37a686726727d3bc3d10aa9) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-setuptools-scm: respect GIT_CEILING_DIRECTORIESEtienne Cordonnier2025-02-182-0/+37
| | | | | | | | | | | | | | | | | | | | | | Fixes https://bugzilla.yoctoproject.org/show_bug.cgi?id=15740 python3-setuptools-scm was ignoring GIT_CEILING_DIRECTORIES which is set by poky, and it was thus finding a wrong value of "toplevel" in ./src/setuptools_scm/_file_finders/git.py The code is supposed to generate the list of files contained in python3-setuptools-scm, but it was instead running "git archive" on whatever git repository was above the build directory, because the tarball containing the sources of python3-setuptools-scm does not contain a .git directory. This is barely noticeable when building as a subdirectory of poky which is only 48MB, but this was causing serious slowdowns of python3-setuptools-scm:do_compile when building inside a big git repository with files tracked using git-lfs (50 minutes in my use-case). Reported upstream as https://github.com/pypa/setuptools-scm/issues/1103 (From OE-Core rev: 4ebe72477484cf68165b6f736ce10373e97d0e6d) Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com> Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-bcrypt: fix ptestChen Qi2025-02-111-10/+0
| | | | | | | | | | | | | | | | For now, python3-bcrypt's ptest package does not have run-ptest script. The ptest-python-pytest.bbclass has do_install_ptest which will generate run-ptest. So the do_install_ptest in pytho3n-bcrypt is not needed, and it does not generate run-ptest. Also remove the RDEPENDS setting because ptest-python-pytest.bbclass has set it. (From OE-Core rev: 9640c89ae0fcc72b53fdf59b01616ab2b62469ed) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: upgrade 3.13.1 -> 3.13.2Peter Marko2025-02-1111-67/+15
| | | | | | | | | | | | | | | Release notes: https://docs.python.org/release/3.13.2/whatsnew/changelog.html#python-3-13-2 Solves CVE-2025-0938, CVE-2024-12254 and 3 other vulnerabilities without CVE number assigment. Remove patch which is included in new release. (From OE-Core rev: 4b91478d47db319af847a45b7d57bb7223da55f8) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-cffi: Fix failing ptests with clangKhem Raj2025-02-112-1/+36
| | | | | | | | | | | | Clang finds additional warnings with cffi generated code _CFFI_test_verify_anonymous_struct_with_star_typedef.cpp:587:10: error: non-constant-expression cannot be narrowed from type 'long' to 'size_t' (ak│a 'unsigned long') in initializer list [-Wc++11-narrowing] (From OE-Core rev: 470edc62b1821bcbb679bd3822acd98e9996c9e7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-typogrify: upgrade 2.0.7 -> 2.1.0Trevor Gamblin2025-02-101-3/+3
| | | | | | | | | | | | | | | | | | | | | License-Update: Update copyright year, attribution bounds The project has changed to using a pyproject.toml with hatchling as the build backend, so change the recipe to match. Changelog (https://github.com/justinmayer/typogrify/releases/tag/2.1.0): - Add ability to select which filters are applied (#1 by davidlesieur & barrysteyn) - jinja_filters: Update import for Jinja 3.1 (by jyelloz) - Ensure all available tests are run (by mcepl) - Package via pyproject instead of Setuptools (by justinmayer) - Improve testing, linting, and CI tooling - Drop support for Python < 3.9 (From OE-Core rev: 037f04b08c76caee6bda176e18c1e0b824f3bcf6) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: add PACKAGECONFIG dependenciesDaniel McGregor2025-02-101-2/+2
| | | | | | | | | | | The cap and acl configs were missing dependency specifications. They could get satisfied transitively if archive was also used, but alone get missed. (From OE-Core rev: 7e89209fd52b1b1652c65013eb3bcc40cb24cda5) Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Drop ld-is-gold supportRichard Purdie2025-02-103-29/+1
| | | | | | | | | | | Gold hasn't seen development in some time and is being dropped from binutils releases. Drop the small number of special cases for it we were carrying. This patch also turns off gold in the binutils recipe. (From OE-Core rev: a4addb9ab63011e7c604fc5daff95559e7d214e7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: upgrade 1.22.11 -> 1.22.12Peter Marko2025-02-107-4/+4
| | | | | | | | | | | | | | | | | | | Upgrade to latest 1.22.x release [1]: $ git --no-pager log --oneline go1.22.11..go1.22.12 5817e65094 (tag: go1.22.12) [release-branch.go1.22] go1.22.12 0cc45e7ca6 [release-branch.go1.22] crypto/internal/fips140/nistec: make p256NegCond constant time on ppc64le c3c6a50095 [release-branch.go1.22] cmd/go/internal/modfetch: do not trust server to send all tags in shallow fetch e0a01acd04 [release-branch.go1.22] cmd/compile: fix write barrier coalescing Fixes CVE-2025-22866 [1] https://github.com/golang/go/compare/go1.22.11...go1.22.12 (From OE-Core rev: 423ad5a67768738dac454b1e2aa27746f74511c5) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Fix to work without gold on aarch64Richard Purdie2025-02-102-0/+50
| | | | | | | | | | If we remove gold from binutils, go-runtime fails to build. There was a workaround in go to use gold as the bfd linker had a bug. The issue was fixed so backport dropping the workaround fmr upstream. (From OE-Core rev: 4636b7206b2e4247835d60956e62f5a2efea9e81) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: fix do_install failed for nativesdk-perlhongxu2025-02-061-1/+1
| | | | | | | | | | | | | | | While set 'baselib = "lib64"' for nativesdk, perl do_install failed: | rm: cannot remove 'tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/ 5.40.0/image//usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/ usr/lib64/perl5/5.40.0/*/CORE/libperl.so': No such file or directory Refer perl class-target do_configure, explicitly pass option '--libdir=${libdir}' to nativesdk do_configure (From OE-Core rev: 68b368c77198c8f6e5f59e7b8a568645240ae426) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix typo in create_manifest3.pyOmri Sarig2025-02-051-1/+1
| | | | | | | | | | Fixed a misspelled "posible" to "possible". (From OE-Core rev: 7e2d743e4809d6cbaa8e441dc42624eb65daad63) Signed-off-by: Omri Sarig <omri.sarig13@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix typo in python3-manifest.jsonOmri Sarig2025-02-051-1/+1
| | | | | | | | | | Fix a wrong "the" to be the intended "that". (From OE-Core rev: fe55f05a7068ba7b277a253058fdcc8964222bc1) Signed-off-by: Omri Sarig <omri.sarig13@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: restore parallel builds, disable lto only for rustdocAlexander Kanavin2025-02-054-28/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | The original reproducibility fix was problematic for a couple reasons: - disabling both lto and parallel builds had an unfortunate effect of nearly doubling rust-native and rust build times (which are slow to begin with). Disabling lto hurts runtime performance too. - both of these things were done for the *entire build*, while the only problematic item is the librustdoc crate. - lto=off option in config.toml has an effect only on building rustc (the compiler itself), and doesn't help with rustdoc reproducibility. Actual fix is the codegen-units setting, which indirectly disables lto via giving llvm only one unit to work with at a time. After some digging, here's a more targeted fix for the problem. Why librustdoc is non-reproducible, but not anything else remains a mystery, hidden deep in rust-llvm's lto optimization code. (From OE-Core rev: a1977407a88a2004c3a6d2dba1d5bfe1aa1664b2) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust/README-rust.md: fix markdown style issuesIgor Opaniuk2025-02-051-11/+13
| | | | | | | | | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat ./meta/recipes-devtools/rust/README-rust.md | mdl (stdin):1: MD002 First header should be a top level header (stdin):25: MD006 Consider starting bulleted lists at the beginning of the line (stdin):3: MD009 Trailing spaces (stdin):11: MD009 Trailing spaces (stdin):26: MD009 Trailing spaces (stdin):39: MD012 Multiple consecutive blank lines (stdin):32: MD032 Lists should be surrounded by blank lines (stdin):36: MD032 Lists should be surrounded by blank lines [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: 62bade83dd6e021f11e9599a2699a1b202324f0f) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: disable ptestsRandy MacLeod2025-02-053-227/+1
| | | | | | | | | | | | | | | | | The valgrind test runner, vg_regtest, changed in the 3.24 update and there are some additional valgrind ptest regressions happening with glibc-2.41. Disable the ptests for now. Some of the remaining patches can likely be dropped but I'd rather carry them so that re-enabling the ptests is simpler. Also the patch series have some dependencies and unwinding that would block the glibc-2.41 unnecessarily. This builds for glibc, musl for qemux86-64, runs: -> valgrind [--leak-check=full] /bin/ls /tmp (From OE-Core rev: 8fc31fb235af12530475ec5055f6c00ccfafadfa) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: update 3.23.0 -> 3.24.0 (ptest fails, vg_regtest needs rebase)Alexander Kanavin2025-02-0519-360/+81
| | | | | | | (From OE-Core rev: 6bf1cd3353c36e12000159e67f3d9212b0cbaf1f) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: Upgrade to 16.2 releseKhem Raj2025-02-054-1/+1
| | | | | | | | | | | | | | | | | | | GDB 16.2 brings the following fixes and enhancements over GDB 16.1: * PR build/32578 (cannot build GDB 16.1 out of tree when calling the configure script with a relative path) * PR tui/32592 ([gdb/tui] internal error in tui-winsource.c:340:refresh_window) * PR remote/32593 (Incompatibilities between GDB's and LLDB's 'x' packet implementation) * PR build/32610 (Missing #include file in darwin_nat.c) (From OE-Core rev: 11362b3ae521a0fba85c034de5ba8d4271574be3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.44 releaseKhem Raj2025-02-0522-599/+491
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* python3-rdflib: upgrade 7.1.1 -> 7.1.3Richard Purdie2025-02-051-2/+2
| | | | | | | | License-Update: copyright years updated. (From OE-Core rev: b90837274d236bf6bf7f79cbd63dd251cab7c453) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: upgrade 19.1.6 -> 19.1.7Richard Purdie2025-02-053-8/+7
| | | | | | (From OE-Core rev: fef54c0109b8abbaaa45c8dc5a022111309f0bd3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 3.31.4 -> 3.31.5Richard Purdie2025-02-056-4/+4
| | | | | | (From OE-Core rev: d7db46a126bc7c7460c99bae512eb435868e27b7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* repo: upgrade 2.50.1 -> 2.51Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 70fdf1f415e7cfe6e66a9b0d8b6e9bc5f34ca0f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-websockets: upgrade 14.1 -> 14.2Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: d609b99f71eb8b3dff186f2dc832918a223a5c16) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-trove-classifiers: upgrade 2024.10.21.16 -> 2025.1.15.22Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 6062b9326d3ff4168a0e5c5932c67c0a9f48f1e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-setuptools: upgrade 75.6.0 -> 75.8.0Richard Purdie2025-02-053-14/+8
| | | | | | (From OE-Core rev: 2f30a782ae5500d9b7dcc37e2cfc43312a470605) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-ruamel-yaml: upgrade 0.18.9 -> 0.18.10Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 0f46b4fd10e6be1c48738e64c24a977a02768c9b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-referencing: upgrade 0.35.1 -> 0.36.2Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: c996952787b26cd3f508db00e82d0bbefdf2675d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pytz: upgrade 2024.2 -> 2025.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: c8445cf5d8e3a47f7ae38d400c7d4edf7d32d3cc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pyopenssl: upgrade 24.3.0 -> 25.0.0Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 98db2721ca2b1edde25cd855f102d1cb7faaa203) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pygments: upgrade 2.19.0 -> 2.19.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 2a5d9af401ff4e8802340eba6382ecd9ce204c7e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-poetry-core: upgrade 2.0.0 -> 2.0.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 911edf7506d6a9eae8ecdbe3ae586b5559f9b6a1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip: upgrade 24.3.1 -> 25.0Richard Purdie2025-02-052-2/+2
| | | | | | (From OE-Core rev: 787b69e38a02c14c8851f110c61366de963bee05) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-more-itertools: upgrade 10.5.0 -> 10.6.0Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 05a7a6dc6c40f5682b4de71f5872e842f4d51441) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-license-expression: upgrade 30.4.0 -> 30.4.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 125af6707480408a2e32ba042ed7bfb4de5f6182) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-hypothesis: upgrade 6.123.2 -> 6.124.7Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: b86720bc7f7d59a9855218cd43ce9850c6e21724) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-certifi: upgrade 2024.12.14 -> 2025.1.31Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 7bfeecb1321171521cb73060f6367467b6084562) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-attrs: upgrade 24.3.0 -> 25.1.0Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 2a4370f0e2c60ff628e548313228655a73a5c878) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtools: upgrade 4.0.46 -> 4.0.47Richard Purdie2025-02-054-7/+7
| | | | | | (From OE-Core rev: 14ef270cc003646e6ca97ff3405507f2b9e92736) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mmc-utils: upgrade to latest revisionRichard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: fc51335605cb2bac4fd9ae293857c71d1b71e3df) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: upgrade 2.47.1 -> 2.48.1Richard Purdie2025-02-053-8/+8
| | | | | | (From OE-Core rev: 0d6d7d63a5e04eaff3db4d6aa552b2bfb3138c9c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unfs3: Use SPDX identifierBastian Germann2025-02-051-1/+1
| | | | | | | | | | | | | The unfs3 license matches the SPDX template for BSD-3-Clause. There is no reason why this should be referenced as unfs3, which is not a registered SPDX identifier. License-Update: use SPDX identifier (From OE-Core rev: e608747d6fba47d2bfc8637adb39ff3593559fca) Signed-off-by: Bastian Germann <bage@debian.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcf-agent: Use SPDX identifierBastian Germann2025-02-051-1/+1
| | | | | | | | | | | | | The EDL-1.0 license matches the SPDX template for BSD-3-Clause. There is no reason why this should be referenced as EDL-1.0, which is not a registered SPDX identifier for exactly this reason. License-Update: use SPDX identifier (From OE-Core rev: 9745740bbab58365f86ef579e1ad1e86b90594a6) Signed-off-by: Bastian Germann <bage@debian.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* docbook-xsl-stylesheets: Use SPDX identifierBastian Germann2025-02-051-1/+1
| | | | | | | | | | | | | The XSL license was standardized by SPDX as DocBook-XML. Copy the license file to the new name and use it in docbook-xsl-stylesheets. License-Update: use new DocBook-XML SPDX ID, copy text from existing XSL (From OE-Core rev: e172e27e19fc09160cfee2a29af8e8c5c2426c9c) 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-019-9/+9
| | | | | | | | | | 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>
* rust-cross-canadian: set CC_<triple> for nativesdkSean Nyekjaer2025-02-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes build errors when building rust bindings for C dependencies for the sdk host. This will allow us to build and run rust programs on the sdk host. Before: % cargo build --target x86_64-oesdk-linux-gnu -vv [...] Compiling zstd-sys v2.0.13+zstd.1.5.6 (zstd-rs/zstd-safe/zstd-sys) [zstd-sys 2.0.13+zstd.1.5.6] CC_x86_64-oesdk-linux-gnu = None [zstd-sys 2.0.13+zstd.1.5.6] CC = Some(arm-oe-linux-gnueabi-gcc -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a7 -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 --sysroot=/usr/local/sdk/sysroots/cortexa7t2hf-neon-oe-linux-gnueabi) [zstd-sys 2.0.13+zstd.1.5.6] cargo:warning=ToolExecError: Command LC_ALL="C" "arm-oe-linux-gnueabi-gcc" "-mthumb" "-mfpu=neon" "-mfloat-abi=hard" "-mcpu=cortex-a7" "-D_TIME_BITS=64" "-D_FILE_OFFSET_BITS=64" "--sysroot=/usr/local/cc-sdk/sysroots/cortexa7t2hf-neon-oe-linux-gnueabi" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "zstd/lib/" "-I" "zstd/lib/common" "-I" "zstd/lib/legacy" "-O2" "-pipe" "-g" "-feliminate-unused-debug-types" "-flto" "-ffat-lto-objects" "-fuse-linker-plugin" "-fvisibility=hidden" "-DZSTD_LIB_DEPRECATED=0" "-DXXH_PRIVATE_API=" "-DZSTDLIB_VISIBILITY=" "-DZDICTLIB_VISIBILITY=" "-DZSTDERRORLIB_VISIBILITY=" "-DZSTD_LEGACY_SUPPORT=1" "-o" "zstd-rs/target/x86_64-oesdk-linux-gnu/debug/build/zstd-sys-b2560022e172eec3/out/44ff4c55aa9e5133-debug.o" "-c" "zstd/lib/common/debug.c" with args arm-oe-linux-gnueabi-gcc did not execute successfully (status code exit status: 1).cargo:warning=arm-oe-linux-gnueabi-gcc: error: unrecognized command-line option '-m64' After: % cargo build --target x86_64-oesdk-linux-gnu -vv [...] Compiling zstd-sys v2.0.13+zstd.1.5.6 (zstd-rs/zstd-safe/zstd-sys) [zstd-sys 2.0.13+zstd.1.5.6] CC_x86_64_oesdk_linux_gnu = Some(x86_64-oesdk-linux-gcc) [...] Compiling zstd v0.13.2 (zstd-rs) Finished dev [unoptimized + debuginfo] target(s) in 14.67s (From OE-Core rev: 3c8fedd6e5a3251b7a7a73cc92b153d8e68cb8e5) Signed-off-by: Sean Nyekjaer <sean@geanix.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: remove redundant cargo config fileHarish Sadineni2025-02-011-14/+0
| | | | | | | | | | | | YOCTO [#15061] The rust target and linker are getting setting from the sdk environment and so the config file is not needed. The redundant config file geneartion is removed. (From OE-Core rev: d5f78816d2ad0f3e43ce883eef199d1683cfcbb4) 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>
* rust: fix for rust multilib sdk configurationHarish Sadineni2025-02-013-9/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | YOCTO [#15061] The rust sdk installs both 'rust.sh' and 'cargo.sh' for lib32 and lib64 in the same location. This causes below error while installing the lib32 & lib64 binaries: Error: Transaction test error: file /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/environment-setup.d/cargo.sh conflicts between attempted installs of rust-cross-canadian-arm-1.67.1-r0.x86_64_nativesdk and rust-cross-canadian-aarch64-1.67.1-r0.x86_64_nativesdk file /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/environment-setup.d/rust.sh conflicts between attempted installs of rust-cross-canadian-arm-1.67.1-r0.x86_64_nativesdk and rust-cross-canadian-aarch64-1.67.1-r0.x86_64_nativesdk ERROR: Task (virtual:multilib:lib32:/media/build/poky/meta/recipes-sato/images/core-image-sato.bb:do_populate_sdk) failed with exit code '1' The change includes: - Prepending '${RUST_TARGET_SYS}' to 'rust.sh' to differentiate between target systems. - Moving the non-target-specific environment variables to 'nativesdk-cargo' and 'nativesdk-rust', instead of being managed by the cross-canadian recipe. (From OE-Core rev: 40eb4bfe2f100ba5301046ca25110fcc55a640bb) 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>
* python3: Update stringold summaryOmri Sarig2025-01-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The string package in python currently contains common string operations. This package is still in full use. However, the old summary line of the package marked it as deprecated. As this is not the case, this commit updates the summary line to better represent this Python package. The new summary line was taken from Python's documentation for the package (https://docs.python.org/3.13/library/string.html). In the past, the string library used to contain functionality that later was moved to the str object in Python. The assumption is that during this change, this library was marked as deprecated here. However, as this package contains more functionality, which is still relevant and used by python, the package itself should not be marked as deprecated. This commit changes the description of the package, but does not change the name of the package. The proper name for this package should be "string" (instead of "stringold"). However, changing the package's name will break compatibility with anyone using the string package in their project. As this is a big change, it is decided not to be done yet. The change in description, as well as this commit message, should be enough to let users understand that the string package in python is still valid, and should not be treated as deprecated. (From OE-Core rev: 7602a9013d6c61959ec293ee29285c90257b5fbb) Signed-off-by: Omri Sarig <omri.sarig13@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: upgrade to 1.7.0Ross Burton2025-01-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Summary of changes: - New custom dependency for atomic - --cap-lints allow used for Cargo subprojects - Cargo features are resolved globally - Meson can run "clippy" on Rust projects - Devenv support in external project module - Fixed sizeof and find_library methods for Fortran compilers - format command now accept stdin argument - "machine" entry in target introspection data - Add new language Linear Asm - Control the number of child processes with an environment variable - Support for Rust 2024 - Support TASKING VX-Toolset - Test targets no longer built by default - Install vcs_tag() output (From OE-Core rev: 37d4a5b2653b94d5030b5026b1ecf979420cfb20) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-04-20 13:27:09 +0000