linux/poky.git/meta/classes-global/sanity.bbclass, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

sanity.bbclass: Remove tool version repetition for gcc, patch, git, make, tar

2025-10-16T09:53:10+00:00

This commit mainly changes the way that error messages are printed when sanity checking for the version numbers of gcc, patch, git, make and tar. It affects the following functions: check_patch_version(), check_make_version(), check_gcc_version(), check_tar_version(), check_git_version() Before this commit, the minimum version number and the error string were hard-coded string literals which the programmer had to maintain manually and independently. With this change, the version is defined once in each function and then used both for checking and for error printing. Additionally, the affected error messages have been made to spill over multiple lines for better source code readability. Link to the relevant discussion: https://lists.openembedded.org/g/openembedded-core/topic/115491380#msg224131 This change has been tested by changing the version string and making sure that the test fails and the proper minimum version is reported in the error message. Suggested-By: Yoann Congal (From OE-Core rev: 27a4ce7b34946200e35adfab1ace512a531fc560) Signed-off-by: Andreas Stergiopoulos Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

sanity: Update minimum gcc version to 10.1

2025-10-02T10:28:02+00:00

Since commit 19004950ad56 ("sanity: Check if the C++ toolchain supports --std=gnu++20") host GCC must support "--std=gnu++20", which became available in 10.1. This is already reflected in the documentation [1] but not here. Update the sanity check on GCC and raise the minimum version to 10.1. Remove the dead link to www.softwarecollections.org. [1]: https://git.yoctoproject.org/yocto-docs/commit/?id=0e538c102bfcb7184c76c2401e8cb878168c4434 Cc: Yoann Congal (From OE-Core rev: 871cc04305fe7483a4c256f38fa63a67cef82183) Signed-off-by: Antonin Godard Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

sanity: Add sanity test for 'bad' gcc installs on ubuntu 24.04

2025-07-09T07:48:04+00:00

Installing emacs on Ubuntu 24.04 pulls in emacs-gtk which leads to libgcc-14-dev despite gcc being 13. This breaks libcxx-native and compiler-rt-native builds. We've tried various ways of addressing this buit they don't work. Instead, detect this situation and tell the user to either install or remove a package. (From OE-Core rev: 087b2730bb2446ad5ea98c233e349d2787c17ff1) Signed-off-by: Richard Purdie

sanity: Reference gcc/g++ directly

2025-07-03T09:40:16+00:00

BUILD_CC and BUILD_CXX can be overridden on a per recipe context now so these tests don't make sense in this form any more. They assume gcc/g++ so lets just use those directly. This fixes things to work with toolchain selection for the native case. (From OE-Core rev: cc93781667cf4f6971bcb9319ab8ab21320852de) Signed-off-by: Richard Purdie

sanity/utils: Directly use gcc, not BUILD_CC

2025-07-03T09:40:16+00:00

The test/helper is written assuming gcc, so just call that and stop accessing BUILD_CC which may be set to clang. (From OE-Core rev: 0a165a93693a293f08cb0d7e2dfa1016803a917a) Signed-off-by: Richard Purdie

bitbake.conf/pseudo: Switch from exclusion list to inclusion list

2025-05-12T21:01:56+00:00

Currently, pseudo tracks all files referenced within its presence unless they're listed in an exclusion list. The exclusion list has grown to be fairly unwieldy. This patch swaps PSEUDO_IGNORE_PATHS for PSEUDO_INCLUDE_PATHS which in theory should be easier and more explicit to maintain. This change does drop many directories from pseudo coverage including /home and /tmp. There may be adapatations needed for recipes/classes using pseudo in specific ways. (From OE-Core rev: 2502da81709f25de499277b28d33c915638c45f6) Signed-off-by: Richard Purdie

sanity: Check if the C++ toolchain supports --std=gnu++20

2025-03-20T17:49:16+00:00

This is needed to build nodejs from meta-oe. Check this early to avoid an error later in the build. Fixes [YOCTO #15804] (From OE-Core rev: 19004950ad5691ef51f7fcf946558bd0de561403) Signed-off-by: Yoann Congal Signed-off-by: Richard Purdie

sanity: Refactor "C++ toolchain support this flag" check

2025-03-20T17:49:16+00:00

This can be use to check for other flags. (From OE-Core rev: 42d012e8414736d89618422fb6f9bce9e4a2a391) Signed-off-by: Yoann Congal Signed-off-by: Richard Purdie

sanity: Bump minimum python version requirement to 3.9

2025-03-20T11:29:04+00:00

Since Ubuntu 20.04 is heading to EoL and that we're having other issues on that platform needing buildtools anyway, we're about to lose the last python 3.8 platform we were supporting. Bump the minimum version to 3.9 since there are many developers wanting access to newer python features. This likely won't be seen since the bitbake minimum has also been increased but helps for documentation purposes. (From OE-Core rev: c3db241c6e97420ca0705d1535a7cdd0c273b761) Signed-off-by: Richard Purdie