linux/poky.git/meta/recipes-devtools, branch 5.2_M2

cmake: upgrade 3.31.3 -> 3.31.4

2025-01-23T12:14:29+00:00

Release notes: https://cmake.org/cmake/help/latest/release/3.31.html#id17 commit log: |tgamblin@megalith ~/workspace/git/cmake (master)$ git log --oneline v3.31.3..v3.31.4 |569b821a13 (tag: v3.31.4) CMake 3.31.4 |92b260387d Merge topic 'duplicate-source-behavior' into release-3.31 |3df8890638 Merge topic 'lfortran-generate-object-code' into release-3.31 |8f45140baf Merge topic 'revert-genex-tco-subgraph' into release-3.31 |3e15419bd4 target_sources: Restore toleration of duplicate CXX_MODULES sources |5cfb8ae790 Tests/CXXModules: add a test with duplicate sources |daf6cc89ee LFortran: Remove hard-coded --generate-object-code flag |a6b84a438f GenEx: Revert "Limit TARGET_PROPERTY transitive closure optimization" |627d710570 Merge topic 'FindBoost-1.87' into release-3.31 |d29855f985 Merge topic 'codegen-help' into release-3.31 |f485f94d1a FindBoost: Add support for Boost 1.87 |45726d93a8 Makefile: List codegen target in help |e7153c29ac Merge topic 'Help-FindPython-Fix-typo' into release-3.31 |e7ea2998fb Help: FindPython: fix typo Reproducibility OK: |2025-01-20 13:52:30,296 - oe-selftest - INFO - Ran 1 test in 1949.827s |2025-01-20 13:52:30,296 - oe-selftest - INFO - OK |2025-01-20 13:52:34,885 - oe-selftest - INFO - RESULTS: |2025-01-20 13:52:34,886 - oe-selftest - INFO - RESULTS - reproducible.ReproducibleTests.test_reproducible_builds: PASSED (1874.21s) |2025-01-20 13:52:34,886 - oe-selftest - INFO - SUMMARY: |2025-01-20 13:52:34,886 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 1949.827s |2025-01-20 13:52:34,886 - oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=1, skipped=0, failures=0, errors=0) (From OE-Core rev: 729611f8284a4b408b8c65a6407daf667571c415) Signed-off-by: Trevor Gamblin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Ross Burton

python3-numpy: upgrade 2.2.1 -> 2.2.2

2025-01-23T11:56:47+00:00

Changelog: https://github.com/numpy/numpy/releases/tag/v2.2.2 Reproducibility looks OK: |2025-01-20 16:40:52,428 - oe-selftest - INFO - Ran 1 test in 2125.833s |2025-01-20 16:40:52,428 - oe-selftest - INFO - OK |2025-01-20 16:40:57,146 - oe-selftest - INFO - RESULTS: |2025-01-20 16:40:57,146 - oe-selftest - INFO - RESULTS - reproducible.ReproducibleTests.test_reproducible_builds: PASSED (2065.94s) |2025-01-20 16:40:57,147 - oe-selftest - INFO - SUMMARY: |2025-01-20 16:40:57,147 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 2125.834s |2025-01-20 16:40:57,147 - oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=1, skipped=0, failures=0, errors=0) (From OE-Core rev: 8ba751635a333ba0ccdeaff7b135131de99292a9) Signed-off-by: Trevor Gamblin Signed-off-by: Richard Purdie Signed-off-by: Ross Burton

gcc-sanitizers.inc: Workaround for aarch64

2025-01-23T11:56:47+00:00

When using the -fsanitize=address CXX_FLAG for a program compiled for aarch64 / arm64 This is happing: MemorySanitizer: CHECK failed: sanitizer_allocator_primary64.h:133 "((kSpaceBeg)) == ((address_range.Init(TotalSpaceSize, PrimaryAllocatorName, kSpaceBeg)))" (0xe00000000000, 0xfffffffffffffff4) (tid=51745) With -DSANITIZER_CAN_USE_ALLOCATOR64=0 this is not happening and potenial bugs are detected. ARM32 does not require this patch. More info about the issue in this thread: https://github.com/llvm/llvm-project/issues/65144 (From OE-Core rev: 12442b9b6df06317174066854935b1d6a4f1865d) Signed-off-by: Thomas Roos Signed-off-by: Richard Purdie Signed-off-by: Ross Burton

tcl8: add a patch to address Y2038 issues (tcl 9.x doesn't need it)

2025-01-23T11:56:47+00:00

(From OE-Core rev: 50731c5233f1531b1a7a9ac94c08235e06be8c2d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie Signed-off-by: Ross Burton

tcl: disable 'zipfs' feature

2025-01-23T11:56:47+00:00

zipfs is a new facility in tcl 9.x where various data files are bundled into a zip archive, rather being separately installed. Then that zip is embedded into libtcl.so from Makefile, thusly: cat ${TCL_ZIP_FILE} >> ${LIB_FILE} This is a major case of face meeting palm: any binary object processing on the resulting .so file discards the extra data at the end, and that's exactly what happens in do_package(), resulting in a tcl installation without any language libraries. This is not caught by ptest because it runs against a private copy of the source tree. Additionally, it helps to have data files on target systems as files that can be viewed and edited. (From OE-Core rev: 05e31be56498123b177f363c700c96b20958585c) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie Signed-off-by: Ross Burton

gcc: make include poisoning fatal again in gcc/g++

2025-01-22T13:20:29+00:00

We have a patch to allow us to 'poison' system include directories, which are warnings by default but we make them fatal in cross builds. However, in the 13.1 upgrade[1] the patch to make the warnings fatal was dropped in the compiler invocation, so it only took effect for pure preprocessor calls. This was not noticed at the time as the test case was flawed, but this has now been fixed. Add back the fatal poisoning, and restructure the patch slightly so it is less invasive. [1] oe-core bea46612fd9106cc5b46eb1d81623b6492563c13 [RP: Tweak to fix gcc/gcc-cross-canadian failure] (From OE-Core rev: 56f21a02c009cb74072ee79467a5bcab3c4643a5) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

python3-cffi: Add missing pkgconfig dependency

2025-01-22T13:20:29+00:00

With gcc posioning fixed, this recipe showed errors, using an incorrect include path looking at the host system. If pkgconfig is present, the correct include paths are used. Therefore add the missing dependency. (From OE-Core rev: 6cf0aaa3af276694709369b6007f629862e21559) Signed-off-by: Richard Purdie

base: Switch virtual/cross-XXX to be under recipe specific providers

2025-01-21T23:09:34+00:00

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

classes/recipes: Switch virtual/XXX-gcc to virtual/cross-cc (and c++/binutils)

2025-01-21T23:09:33+00:00

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

fmt: fix build with GCC 9.4

2025-01-21T13:26:07+00:00

fmt-native is needed to build ccache-native, and the compile fails on hosts with GCC 9.4 (such as Ubuntu 20.04). Backport a patch to fix this issue. (From OE-Core rev: 7dbb984f86d04e79d2311411cd8b775e2674b5f3) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie