linux/poky.git/meta/files, branch 5.2_M3

toolchain-shar-relocate.sh: support multiple dynamic loaders for multilib

2025-02-11T11:44:19+00:00

While nativesdk support multilib, there are two dynamic loaders, $OECORE_NATIVE_SYSROOT/lib64/ld-linux-x86-64.so.2 $OECORE_NATIVE_SYSROOT/lib/ld-linux.so.2 Search them with wildcard and call relocate_sdk.py separately [ YOCTO #15722 ] (From OE-Core rev: 703187755244b1a45dd9f90aeaf620d4c92a6757) Signed-off-by: Hongxu Jia Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: Enable '-o pipefail' for the SDK installer

2025-02-05T13:00:45+00:00

When testing a Yocto SDK installer on Alpine 3.21, we recently ended up with a broken SDK. One of the commands the relocation script calls in a piped multi-command chain failed (see [0]), but the installer did not realize that - since it doesn't use 'set -o pipefail'. Thus, the error was never reported to the user and the installer claimed to have set up the SDK correctly - which wasn't the case. Given that the SDK installer is a POSIX-compliant shell script and that the 'pipefail' option used to be missing from the standard, it's not surprising that it isn't used. Thankfully however, in June of 2024, a new version of POSIX (POSIX.1-2024) was released - and that one finally includes the 'pipefail' option (see [1]). A number of shells already support it, so let's enable it if available to make the SDK installer more robust. The change has been tested locally using SDK installers for internal projects, based on both Kirkstone and Scarthgap. [0]: https://gitlab.alpinelinux.org/alpine/aports/-/issues/16797 [1]: https://pubs.opengroup.org/onlinepubs/9799919799.2024edition/utilities/V3_chap02.html#set (From OE-Core rev: 1cb4b41c7faf77fcc347b1276d86d4288968c926) Signed-off-by: Moritz Haase Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

docbook-xsl-stylesheets: Use SPDX identifier

2025-02-05T12:49:55+00:00

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 Signed-off-by: Richard Purdie

files: overlayfs-create-dirs: Improve mount unit dependency

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

The RequiresMountsFor configuration option of systemd.unit (added in systemd version 201) not only adds the Requires and After options for the required mount unit, but it adds them for all mount units required to access the specified path. So this change is both a simplification, and an improvement. Not only will all needed mount units be added to Requires and After, but the overlay path does not have to be a mountpoint, but can be at any directory level beneath a mountpoint. (From OE-Core rev: fa2422232a143b21aeea3728abca82100946dbc4) Signed-off-by: Esben Haabendal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Ross Burton

classes/ptest-python-pytest: simplify python ptest file overriding

2025-01-14T11:57:52+00:00

The complexity of overriding files from the bbclass made the behavior at times hard to follow and predict. This change replaces the default file with a heredoc equivalent that creates a default file if the user does not provide their own version of run-ptest in the SRC_URI. (From OE-Core rev: be3db5f4f1b857b93d08211019d9ff796ec389b6) Signed-off-by: Derek Straka Signed-off-by: Richard Purdie

classes/ptest-python-pytest: add a new class to consolidate pytest ptest functionality

2025-01-08T12:37:20+00:00

A large number of python packages leverage the pytest unit test framework for their ptest functionality. Currently, many of the tests have duplicate code for: 1. Installing pytest files 2. Declaring ptest dependencies 3. Script for executing tests (run-ptes) To simplify adding common pytest based ptests, added a new class enabling base functionality. Users can also override the location of the pytest files in addition to using their own version of run-ptest [RP: Minor whitespace tweaks to shell function and missing prepend space] (From OE-Core rev: d66009e608256d42b2d6573d4614a99eb13fd3f1) Signed-off-by: Derek Straka Signed-off-by: Richard Purdie

toolchain-shar-relocate.sh: fix the replacing commands

2024-12-09T15:23:28+00:00

There're two cases that the current replacing commands cannot handle well: 1. Files with whitespace in their names 2. Installation path with keyword such as 'script' This results in installation failure of a buildtools. We can use the following commands to reproduce the problem. 1. bitbake buildtools-tarball 2. ./tmp/deploy/sdk/x86_64-buildtools-nativesdk-standalone-5.1.sh -d dir-with-keyword-script -y The error message is like below: Setting it up...sed: can't read /PATH/TO/dir-with-keyword-script/sysroots/x86_64-wrlinuxsdk-linux /usr/lib/python3.13/site-packages/setuptools/_vendor/jaraco/text/Lorem: No such file or directory Failed to replace perl. Relocate script failed. Abort! The actual file name is /PATH/TO/dir-with-keyword-script/sysroots/x86_64-pokysdk-linux/usr/lib/python3.13 /site-packages/setuptools/_vendor/jaraco/text/Lorem ipsum.txt Note that the file path matches "script.*text". In fact, if we install the SDK into some directory containing both 'script' and 'text', all files will be matched. This is not expected. This patch fixes the replacing commands by doing the following two things: 1. Use '\n' as the field separator for xargs so that files with white spaces are not splitted. 2. Use awk to match the second filed of the file command's output so that the file path does not mess up with the matching process. (From OE-Core rev: 443912d512edbb75f16c52de489b33b6f8687431) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

linux-yocto: add and use GPL-2.0-with-syscall-note license

2024-12-05T17:07:10+00:00

See Linux COPYING, LICENSES/preferred/GPL-2.0 and LICENSES/exceptions/Linux-syscall-note. (From OE-Core rev: 762aecc750229047394be72ea2a5bbcb86a1cef0) Signed-off-by: Denis Osterland-Heim Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

files: Amend overlayfs unit descriptions with path information

2024-10-29T11:19:57+00:00

Having something like Starting Overlayfs directories setup /home... Starting Overlayfs directories setup /root... Finished Overlayfs directories setup /home. Finished Overlayfs directories setup /root. Mounting Overlayfs mount unit /home... Mounting Overlayfs mount unit /root... Mounted Overlayfs mount unit /root. Mounted Overlayfs mount unit /home. is much more informative than Starting Overlayfs directories setup... Starting Overlayfs directories setup... Finished Overlayfs directories setup. Finished Overlayfs directories setup. Mounting Overlayfs mount unit... Mounting Overlayfs mount unit... Mounted Overlayfs mount unit. Mounted Overlayfs mount unit. Especially as the number of overlayfs mount units increase. (From OE-Core rev: 7308b4fc6f51bdf2b8f3b7899ff3758c5968e418) Signed-off-by: Esben Haabendal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: support tar.zst SDK_ARCHIVE_TYPE

2024-10-28T11:58:22+00:00

zst is much faster than the default xz, test result on my Precision 5680 machine: Installing a tar.xz SDK takes 37 seconds while tar.zst only takes 17 seconds. Let's introduce support for tar.zst. Also add a sanity check for supported archive types. (From OE-Core rev: 1d22562a89e91f19b818b8f9bc214be941303980) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie