summaryrefslogtreecommitdiffstats
path: root/meta/files
Commit message (Collapse)AuthorAgeFilesLines
* classes/ptest-python-pytest: add a new class to consolidate pytest ptest ↵Derek Straka3 days1-0/+3
| | | | | | | | | | | | | | | | | | | | | functionality 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 <derek@asterius.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-relocate.sh: fix the replacing commandsChen Qi2024-12-091-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: add and use GPL-2.0-with-syscall-note licenseDenis OSTERLAND-HEIM2024-12-051-0/+357
| | | | | | | | | | | 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 <denis.osterland@diehl.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: Amend overlayfs unit descriptions with path informationEsben Haabendal2024-10-292-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <esben@geanix.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: support tar.zst SDK_ARCHIVE_TYPEMing Liu2024-10-281-0/+6
| | | | | | | | | | | | | | | | | 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 <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract.sh: check required tool before extracting SDKMing Liu2024-10-281-0/+8
| | | | | | | | | | | To extract the SDK archive, the proper tools need to be present on system, check unzip for zip archive type, check xz for tar.xz archive type. (From OE-Core rev: 718328588e832c0a59dc9b76ff4e5e3def6e8834) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract.sh: replace which with "command -v"Ming Liu2024-10-281-3/+3
| | | | | | | | | | Command 'which' is not POSIX or even universally installed on Linux systems, replace it with 'command -v'. (From OE-Core rev: f604e059bdf0ebd23f4b9c6af3f6249c9acdc551) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract.sh: exit when post-relocate-setup.sh failsChen Qi2024-10-111-0/+4
| | | | | | | | | | | | | | When LD_LIBRARY_PATH is set, post-relocate-setup.sh will fail and exit properly. But such failure is ignored and the SDK installation will continue and tell user that things succeed. This is misleading. So exit immediately if post-relocate-setup.sh fails. Fixes [Yocto #15586] (From OE-Core rev: c8e2dcc1f71aa33cc6e56dfdebebbe7ef010c944) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: drop VOLATILE_TMP_DIR, use FILESYSTEM_PERMS_TABLES insteadChangqing Li2024-08-282-2/+38
| | | | | | | | | | | | | | | | * Drop VOLATILE_TMP_DIR, use FILESYSTEM_PERMS_TABLES instead. By default, FILESYSTEM_PERMS_TABLES ?= "files/fs-perms.txt \ files/fs-perms-volatile-log.txt \ files/fs-perms-volatile-tmp.txt" it contains 'files/fs-perms-volatile-tmp.txt', which means volatile tmp is enabled. User can disable volatile tmp by remove 'files/fs-perms-volatile-tmp.txt' from FILESYSTEM_PERMS_TABLES. * If volatile tmp is disabled, both /tmp and /var/tmp are persistent (From OE-Core rev: 8d1ae67b89c45f78162e070228086c7ef88c3264) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: drop VOLATILE_LOG_DIR, use FILESYSTEM_PERMS_TABLES insteadChangqing Li2024-08-282-33/+1
| | | | | | | | | | | | Drop VOLATILE_LOG_DIR, use FILESYSTEM_PERMS_TABLES instead. By default, it contains 'files/fs-perms-volatile-log.txt', which means volatile log is enabled. User can disable volatile log by remove 'files/fs-perms-volatile-log.txt' from FILESYSTEM_PERMS_TABLES. (From OE-Core rev: 91128c6517066715f2afe6b46aa3206c7cf3653e) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* licenses: Update to SPDX license version 3.24.0Joshua Watt2024-07-02185-3935/+12107
| | | | | | | | | | | | Updates to the latest version of the SPDX license list and pulls in all the missing license files [YOCTO #15502] (From OE-Core rev: e9c1f48af10ccb58251ecc7e041babb99b94d6df) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk: Fix path length limit to match reserved sizeRobert Kovacsics2024-05-141-1/+3
| | | | | | | | There were two different interpreter lengths in use, make them match. (From OE-Core rev: b175f9cdc3d87bef5c89cc337c2a7e2674732b29) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-relocate.sh: Add check for missing command 'file'Tom Hochstein2024-03-231-4/+6
| | | | | | | | | | | | | | | | | | | | | | On a machine without the file command, the SDK install fails with a cryptic error message. ``` xargs: file: No such file or directory sed: no input files Failed to replace perl. Relocate script failed. Abort! ``` Add a test for 'file' to print a clear error message. ``` The command 'file' is required by the relocation script, please install it first. Abort! ``` (From OE-Core rev: 1aa19b9e34ebe6f39a25364073fed4c069f650e8) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* screenshot-tests: Add initial screenshot test png files for core-image-satoEilís 'pidge' Ní Fhlannagáin2024-03-0716-0/+8
| | | | | | | | | | | | | This is an initial commit of png's we can use to test qemu image testing against. Also add symlinks for core-image-sato-sdk [RP: Add symlinks and missing image] (From OE-Core rev: 06b7a8c02fbf89258034a0a258efc0bd23902f03) Signed-off-by: Eilís 'pidge' Ní Fhlannagáin <pidge@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs-etc: add option to skip creation of mount dirsbaruch@tkos.co.il2024-02-191-7/+9
| | | | | | | | | | | | | The 'preinit' script can't create mount directories when rootfs is read-only. Add an option to skip this step. The user must make sure that all required directories are already in the rootfs directory layout. Cc: Vyacheslav Yurkov <uvv.mail@gmail.com> (From OE-Core rev: 3d433d8559467d255bd19af2d0999c65ea24a48d) Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-relocate: allow 'find' access to libraries in symlinked ↵Maanya Goenka2024-02-081-1/+2
| | | | | | | | | | | | | | | directories If the '/' is not added to the end of the dynamic loader path, only directories that are not symlinks will be looked into for libraries such as ld-linux*, so the slash is added to allow the 'find' command to have symlinked directory access too. (From OE-Core rev: 8468f24e3e81d5248eb1424e43accd2ea8bf0568) Signed-off-by: Maanya Goenka <maanyagoenka@microsoft.com> Signed-off-by : Alejandro Hernandez Samaniego <alhe@linux.microsoft.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop oldincludedirRichard Purdie2023-11-202-2/+0
| | | | | | | | | | | | | | | | | | | Autoconf defines this as: "The directory for installing C header files for non-GCC compilers." Whilst this is something autoconf does allow changing, I find it hard to believe it has much use in the wild now and that headers don't get split like this in reality, it would probably only be useful on really old unixes.. The values are the same in our configuration anyway. Drop the value and just use includedir everywhere. (From OE-Core rev: 506c91cbc6a604a84e37e53ccff430436369802e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-sysroots: target or native sysroot population need to be selected ↵Alexander Kanavin2023-09-091-1/+1
| | | | | | | | | | | | | | | | | explicitly Running them in parallel is prone to races as postinsts from target sysroots rely on executables from native sysroots which may or may not be fully prepared yet. This was observed for example here: https://autobuilder.yoctoproject.org/typhoon/#/builders/146/builds/468/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/147/builds/467/steps/12/logs/stdio (From OE-Core rev: 38d7a2e45b883cf999a86af05bcc0eaa875bb47c) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses: Add LGPL-3.0-with-zeromq-exceptionRemi Peuvergne2023-06-131-0/+181
| | | | | | | | | | ZeroMQ is not exactly LGPL-3.0 and has a specific exception. (From OE-Core rev: 21b08f04a1eda343e230c01ef1993ace81614f3c) Signed-off-by: Remi Peuvergne <remi.peuvergne@non.se.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes: files: Extend overlayfs-etc classVyacheslav Yurkov2022-09-091-0/+9
| | | | | | | | | | | | | Add the ability to expose the lower layer of /etc when mounting overlay. This is the similar to what overlayroot script from initramfs-framework does. By default, this option is turned off to keep an old behavior intact. (From OE-Core rev: 791e8a8bacce5a7f31f4d7bcbfb17df2967fd258) Signed-off-by: Vyacheslav Yurkov <v.yurkov@precitec.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: overlayfs-etc: refactor preinit templateVyacheslav Yurkov2022-09-091-5/+9
| | | | | | | | (From OE-Core rev: ad5b2bffbee6ddcf51bc146d1e76c980b498b399) Signed-off-by: Vyacheslav Yurkov <v.yurkov@precitec.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/files/layers.schema.json: drop the layers propertyAlexander Kanavin2022-09-022-39/+0
| | | | | | | | | | | | | | | | | This is a leftover from one of the RFC iterations, where the property contained available machines, distros and templates. As all of those were dropped from the final version, there is no reason to list the layers either anymore. Normally this would be a backwards incompatible change, but as the layer setup itself was just merged, I think we can do a quick fixup :-) (From OE-Core rev: 64a774de0e154ef81f20853fec903b17d9985a72) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/files: add layer setup JSON schema and exampleJoshua Watt2022-09-012-0/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Defines a common schema for layer setup that can be consumed by tools to know how to fetch and assemble layers for end users. Also includes an example of the layer setup that constructs poky/meta-intel/imaginary product layer for reference. The schema can be used to validate a layer setup file with the commands: $ python3 -m pip install jsonschema $ jsonschema -i meta/files/layers.example.json meta/files/layers.schema.json (From OE-Core rev: 72740b5dd635579e373b4bfe6ccacfe6a02aa998) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Alex: I made the following modifications to Joshua's original commit: - moved the files from meta/lib to meta/files - the example json showcases a multi-repo, multi-layer setup instead of just poky - closer to a typical product - added oe-selftest that validates the example json against the schema using python3-jsonschema-native - the schema is modified so that: -- all lists (sources, layers, remotes) are replaced by objects keyed by 'name' properties of the list items. This allows using them as dicts inside Python, and makes the json more compact and readable. -- added 'contains_this_file' property to source object -- replaced 'remote' property with a 'oneOf' definition for git with a specific 'git-remote' property. 'oneOf' is problematic when schema validation fails: the diagnostic is only that none of oneOf variants matched, which is too non-specific. -- added 'describe' property to 'git-remote' object. -- removed description property for a layer source: it is not clear how to add that when auto-generating the json Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: respect overlayfs owner from lower layerVyacheslav Yurkov2022-06-041-0/+3
| | | | | | | | | | | Permission model of overlayfs uses permissions/ownership from the upper layer after mounting. Fix up UID/GID of the upper layer, when lower layer already uses something custom. (From OE-Core rev: b19b734ec3c031ee594229e728ee077cd58b34a9) Signed-off-by: Vyacheslav Yurkov <v.yurkov@precitec.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: rootfs-postcommands: move helper commands to scriptVyacheslav Yurkov2022-06-042-2/+9
| | | | | | | | | | | | OverlayFS systemd helper unit might require more pre-processing commands. It gets more complicated to embed them in a unit file, because systemd shell subset is limited and might require additional escaping. Move the command to a separate script, thus simplifying systemd unit. (From OE-Core rev: 86a457016e7f3fc7acacf86cd87f5d8d882132dd) Signed-off-by: Vyacheslav Yurkov <v.yurkov@precitec.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: overlayfs-etc: add overlay mount options to preinitClaudius Heine2022-03-111-0/+1
| | | | | | | | | | | | | | | | | Overlayfs-etc is useful if the rootfs is read-only. One reason to have the rootfs read-only is to allow image based updating. Image based updating will change the underlying root file system, which is unsupported by overlayfs when with some mount options [1]. This disables those options. [1] https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html?highlight=overlayfs#changes-to-underlying-filesystems (From OE-Core rev: 13a057d6ffc3110f891224d7af9455b53581e8a8) Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: overlayfs-etc: wrap long lines of preinit fileClaudius Heine2022-03-111-2/+9
| | | | | | | | | | Make it easier to see what is happening by wrapping the overly long lines in the preinit file for the overlayfs-etc. (From OE-Core rev: 2e116bbc1afbc571b99f2605839e3c90839471be) Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: overlayfs-create-dirs: split ExecStart into two commandsStefan Herbrechtsmeier2022-02-251-1/+2
| | | | | | | | | | | | | | Split ExecStart into two commands because systemd interpret an ExecStart entry as a single executable with multiple parameters. systemd[1]: Starting Overlayfs directories setup... mkdir: cannot create directory '&&': Read-only file system mkdir: cannot create directory 'mkdir': Read-only file system (From OE-Core rev: 209204f7f9d294543fd57b90e29a95c2cde66d99) Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk: fix search for dynamic loaderChristian Eggers2022-02-121-1/+1
| | | | | | | | | | | | | | | | | | | if the package "nativesdk-glibc-dbg" is installed as part of the SDK, the existing search expression finds two files: $OECORE_NATIVE_SYSROOT/lib/.debug/ld-linux-x86-64.so.2 $OECORE_NATIVE_SYSROOT/lib/ld-linux-x86-64.so.2 The generated relocate_sdk.sh shell script contains then an extra newline and segfaults during SDK relocation. Limit the search depth to 1, to avoid finding the file in the .debug directory. (From OE-Core rev: baec04b936ab6b3d2039978fd568c3824cd0a501) Signed-off-by: Christian Eggers <ceggers@arri.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licences: remove ambiguous "BSD" licenseRoss Burton2022-02-071-26/+0
| | | | | | | | | | | | | | | | Our "BSD" license is the 3-clause BSD license, but many recipes were using "BSD" for any variation of the license. We've mostly moved recipes away from the vague "BSD" license to concrete names such as "BSD-3-Clause", so delete the BSD license to force the remaining users to update their license statements. [ YOCTO #14539 ] (From OE-Core rev: 14d4c007c49652d836d325a12bdbcd3bfa42e6d5) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs: move templates to files directoryVyacheslav Yurkov2021-12-123-0/+39
| | | | | | | (From OE-Core rev: b08ce6d23f2c6c89073ddff90b758360f9ce9fea) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: add overlayfs-etc-preinit.sh.inVyacheslav Yurkov2021-12-121-0/+29
| | | | | | | | | A template init script for overlayfs-etc class (From OE-Core rev: c0173002f3f2118f72307b7e60515287a1b56bda) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust-common.bbclass: rewrite toolchain wrappers in (native) pythonAlexander Kanavin2021-10-141-29/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | librsvg on centos 7 and friends exhibits the same libtinfo leakage problem, this time coming from the compiler and not the linker. Simply covering the compiler by the existing C wrapper-of-wrapper does not work, as rust-native builds put Important Stuff into LD_LIBRARY_PATH and unsetting it breaks things badly. Rather than try to figure out which combination of wrappers and LD_LIBRARY_PATH settings works for which situation, or provide some kind of sh-native, let's simply use python3-native for the wrappers, which should insulate builds from the the host shell. rust-native already depends on python3-native, so this does not lengthen the builds. This also reverts: rust-common: Hack around LD_LIBRARY_PATH issues on centos7 (commit 63b1fd2226b5f146d6c853cc57417704df378438). I'd also like to say boo to Red Hat (or GNU?) for breaking ABI compatibility for stat() in glibc 2.33, we ended up sorting this mess because of it. (From OE-Core rev: 997d54363a3cb3a0e949b3626855f2fa41afeb2b) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spdx-licenses.json: Use 3.14 tagged versionSaul Wold2021-09-281-1283/+1282
| | | | | | | | | | The validation tools expect the licenseListVersion to be a proper X.Y version, not an intermedite git hash version. (From OE-Core rev: b96bb3fe6e17a194db0dcb86d2877946eaa77341) Signed-off-by: Saul Wold <saul.wold@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses, licenses.conf: Remove duplicate licensesPeter Kjellerstedt2021-09-065-353/+0
| | | | | | | | | | | | This removes BSD-0-Clause, Nauman, tcl and vim and adds mappings for them to their SPDX counterparts (0BSD, Naumen, TCL and Vim). It also removes FreeType, which already had a mapping to FTL. (From OE-Core rev: 35d699c479b6ce6acafbf75fb003618aaad094d7) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add SPDX licensesJoshua Watt2021-09-031-0/+5938
| | | | | | | | | Adds the SPDX license database from https://github.com/spdx/license-list-data (From OE-Core rev: a8048931701438e2f267a52a43869c27743907e3) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses: add missing SPDX licencesRoss Burton2021-09-03294-0/+19147
| | | | | | | | | | As part of the work to converge our license support with SPDX, ensure that we have all of the licenses that SPDX supports. (From OE-Core rev: e2f9092c37395f4e3ee9d0777e28c83cce6007ee) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust-common: Hack around LD_LIBRARY_PATH issues on centos7Richard Purdie2021-09-021-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When building cargo-native on centos7 with buildtools tarball installed, we see failures: /bin/sh: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by /home/pokybuild/yocto-worker/reproducible-centos/build/build-st/tmp/work/x86_64-linux/cargo-native/1.54.0-r0/recipe-sysroot-native/usr/lib/libtinfo.so.5) We also see this for libstd-rs once cargo-native is fixed. The reason for this is that the wrapper script cargo-native/1.54.0-r0/wrapper/target-rust-ccld has /bin/sh as it's interpreter and cargo calls this with LD_LIBRARY_PATH set to include the recipe-sysroot-native. The host /bin/sh links to libtinfo from the host but it finds the version in the sysroot which needs a newer libc. This results in the above error since the loader is an older libc and the two are incompatible. Our ccld wrapper calls gcc/ld which don't need the LD_LIBRARY_PATH variable set. We can't patch this out the source since we're using a prebuilt binary to generate a new cargo binary so this is impossible to bootstrap. Instead, put a binary wrapper into place which removes LD_LIBRARY_PATH from the environment before calling the original wrapper (left in shell as it is simpler to maintain). (From OE-Core rev: 8feeeb7f76c6725e5226458c8f22999b67c52694) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk: fix relocate symlink failedhongxu2021-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Install SDK to non-default dir, sysmlink mkfs.vfat is invalid $ ./sdk.sh -y -d ./dnf-2 -S -D $ ls sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat -al lrwxrwxrwx 1 hjia users 99 Aug 10 20:38 sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat -> /opt/windriver/wrlinux-graphics/21.32/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat.dosfstools Since commit [bc4ee54535 sdk: Decouple default install path from built in path] applied, sdk relocates symlink failed, it should replace $SDK_BUILD_PATH rather than $DEFAULT_INSTALL_DIR, just like above commit did Without this commit: ... |+ for l in $($SUDO_EXEC find $native_sysroot -type l) |++ readlink path-to/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat |++ sed -e s:/usr/local/oecore-x86_64:path-to: |+ ln -sfn /opt/windriver/wrlinux-graphics/21.32/sysroots/x86_64-wrlinuxsdk-linux/ usr/bin/mkfs.vfat.dosfstools path-to//sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat ... After appling this commit: ... |+ for l in $($SUDO_EXEC find $native_sysroot -type l) |++ readlink path-to/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat |++ sed -e s:/opt/windriver/wrlinux-graphics/21.31:path-to: |+ ln -sfn path-to/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat.dosfstools path-to/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/mkfs.vfat ... (From OE-Core rev: 942c06a7348070b92f722fa5c439c8c4404485b7) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk: Decouple default install path from built in pathRichard Purdie2021-08-022-2/+3
| | | | | | | | | | | | | | Add SDKPATHINSTALL which is used as the default install location of the SDK instead of SDKPATH. This means the default install path isn't encoded into every SDK binary, meaning if a date is used there the entire SDK doesn't have to rebuild. Most distros can switch to only customise SDKPATHINSTALL meaning more sstate reuse too. [YOCTO #14100] (From OE-Core rev: bc4ee5453560dcefc4a4ecc5657df5cc1666e153) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: Add support for PR serviceMark Hatle2021-03-311-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | In the classes/populate_sdk_ext.bbclass the system already copies a number of configurations, such as the hash equivalency data. However, the PR service was being handled. The new code works by checking if PRSERV_HOST is defined, if it is, use the existing export functions to write out a conf/prserv.inc file into the eSDK. On eSDK install, if a conf/prserv.inc file is present we then import this file into the system. This mechanism will work if the PRSERV_HOST is local or remote, as it pulls the necessary data from the server and then imports it to a local database on eSDK installation. Note: the conf/prserv.inc file is not deleted at this time. It was left for possible debugging purposes, but removing it is something we could decide to do in the future. (From OE-Core rev: e207dabdfaa07cd5ebba1cd7dd58610f7185c7e2) Signed-off-by: Mark Hatle <mark.hatle@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest-perl/run-ptest: address failures caused by perl 5.32.1Alexander Kanavin2021-03-021-1/+1
| | | | | | | | | | Particulary, . needs to be explicitly specified so that perl looks there when loading items in 'require'. (From OE-Core rev: 324d74c7e541b44b9c4240056b006f4c59ef34af) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* licenses: Update license file to match current SPDX namesMeh Mbeh Ida Delphine2021-02-2114-0/+2866
| | | | | | | | | | | | | | | | | | | | * Updated mappings of license fields of meta/conf/licenses.conf to match latest SPDX naming. * Add mappings to the old names * Renamed license files to match the new preferred names. * Added "or later" versions of license mappings * Added "or later" versions of common license files eg GPL-2.0-or-later Fixes: [YOCTO #13320] (From OE-Core rev: 5ecf139a31fa7bd813855f1235ea9f434fbcb2e0) Signed-off-by: Meh Mbeh Ida Delphine <idadelm@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses: Add GPL-3.0-with-bison-exceptionJose Quaresma2021-01-231-0/+7
| | | | | | | (From OE-Core rev: 58f8debdd53c27cce17ae083dfeb0dab0bd54964) Signed-off-by: Jose Quaresma <quaresma.jose@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-relocate.sh: Fix handling files with colonsOleksiy Obitotskyy yIEf0zt.mo2021-01-201-1/+1
| | | | | | | | | | | Files could contain colons in name and we should not use colons (':') as field separator. E.g. perl/python man pages packages. (From OE-Core rev: 50d2ed0689f1aed6f33b4992d37e2e991c99eb07) Signed-off-by: Oleksiy Obitotskyy <oobitots@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract.sh: Handle special characters in script pathAndrey Mozzhuhin2021-01-171-6/+6
| | | | | | | | | | | | | Extracting SDK archive may fail if the script is run using a path with special characters such as space or asterisk. This is because the shell interprets such characters after expanding the $0 variable. Added quotes to all uses of the shell variable $0 to fix this. (From OE-Core rev: 0453acbbd45604537090ec7a3295b34309e6eecb) Signed-off-by: Andrey Mozzhuhin <amozzhuhin@yandex.ru> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses: add BSD-3-Clause-Clear licenseAdrian Herrera2021-01-151-0/+32
| | | | | | | | | | See https://spdx.org/licenses/BSD-3-Clause-Clear.html (From OE-Core rev: 6db06326d2d6ba68cee5ddc24eeaa6eccb441666) Signed-off-by: Adrian Herrera <adrian.herrera@arm.com> Change-Id: I2b7e0ad060fac6b473ce4d0bab839253aee9873d Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: toolchain-shar-relocate.sh: Filter out post-relocate-setup scriptMarek Vasut2021-01-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | The toolchain-shar-extract.sh script updates the SDK relocation paths in post-relocate-setup.sh, so avoid doing this twice. This is generally not a problem, unless the SDK path is a subset of the SDK relocation path, in which case the resulting path is substituted twice. To trigger the issue, $ ./tmp/deploy/sdk/poky-glibc-x86_64-core-image-base-core2-64-qemux86-64-toolchain-3.2+snapshot.sh -y -d /home/oe/.local/opt/poky/3.2+snapshot which generates relocation path /home/oe/.local/home/oe/.local/opt/poky/3.2+snapshot instead of /home/oe/.local/opt/poky/3.2+snapshot Fixes: 93ec145f42 ("toolchain-shar-extract: Add post-relocate scripts") (From OE-Core rev: 5000aabe6ac336e7b424dafa1bf76271dee6a6f1) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Krzysztof Zawadzki <krzysztof.zawadzki@nokia.com> Cc: Randy Witt <randy.e.witt@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: toolchain-shar-relocate.sh: Do not use $target_sdk_dir as regexMarek Vasut2021-01-121-1/+3
| | | | | | | | | | | | | | | | | | | | | The $target_sdk_dir path might contain special characters, for example if the path is /opt/poky/3.2+snapshot . Prevent grep from interpreting those as part of the regex by using the -F parameter and multiple -e parameters to specify which strings to filter out. Also note that the previous regex was using asterisk as wildcard (e.g. environment-setup-*), but that should have been regex (e.g. environment-setup-.*, with dot) to match correctly, this is also fixed by this change. Fixes: 9721378688 ("toolchain-shar-template.sh: Make relocation optional.") (From OE-Core rev: 19d9fa7ab6c851000bc5d24281739e1b2bb8f057) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Krzysztof Zawadzki <krzysztof.zawadzki@nokia.com> Cc: Randy Witt <randy.e.witt@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fs-perms: Ensure /usr/src/debug/ file modes are correctRichard Purdie2020-11-242-2/+2
| | | | | | | | | | | | | | | | | If files are copied into /usr/src/debug directly from WORKDIR (e.g. makedevs) we'd get the permissions from the checkout which would depend on the host umask. Avoid this and be deterministic by setting the file modes consistently. Core code copies the files in so we're responsible for the permissions. Unfortunately to force this change to apply we need to invalidate both the package tasks and the hash equivalance mappings since file mode 'corruption' already made it into the output hashes (both input options were mapped to the output hashes). (From OE-Core rev: 1f958bcd6c9cd12ec76d80586cba15f4d6ed17a7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-11 01:54:50 +0000