summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2023-02-27scripts/runqemu: move render nodes check to runqemu from selftestAlexander Kanavin
This will produce a more useful hint for those setting up or testing virgl headless: runqemu - ERROR - No render nodes found in /dev/dri: ['by-path', 'card0']. If /dev/dri/renderD* is absent due to lack of suitable GPU, 'modprobe vgem' will create one suitable for mesa llvmpipe software renderer. as qemu itself isn't helpful: alex@Zen2:/srv/storage/alex/yocto/build-64-alt$ qemu-system-x86_64 -display egl-headless qemu-system-x86_64: egl: no drm render node available qemu-system-x86_64: egl: render node init failed (From OE-Core rev: cbbada6a6c9b0a2e97f7395117dad986555f2db9) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-27selftest: do not check for dri.pc in the headless testAlexander Kanavin
runqemu (which the test also runs) already performs this check, and does it better, as it additionally unsets a number of environment variables that can confuse and misdirect host's pkg-config. (From OE-Core rev: ad179728a6978d929e2a876abe7e1cbd6b76a502) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-27build-appliance-image: Update to master head revisionRichard Purdie
(From OE-Core rev: f6ac666c99da115ab4a214d24282978a06c36efa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26resulttool/regression: Improve matching of poor ptest test names4.2_M3Richard Purdie
Some test case naming is poor and contains random strings, particularly lttng/babeltrace but also curl. Truncating the test names works since they contain file and line number identifiers which allows us to match them without the random components, or in the case or curl, test IDs. Going forward we may be able to improve the test names but this tweak allows historical test results to work in reports. (From OE-Core rev: 541a2e2683531355e678fd93524a0c4a8c43a8ff) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26resulttool/regression: Ensure LTP results are only compared against other ↵Richard Purdie
LTP runs If a test result contains LTP test results, it should only be compared with other runs containing LTP test results. (From OE-Core rev: 4dbbf2f4a85620a08dc2fa65095dc17fe6c530f8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26oeqa/selftest: add test for yocto_testresults_query.pyAlexis Lothoré
Add some tests for new yocto_testresults_query.py helper. First test is taken from yocto-autobuilder-helper feature which has moved in yocto_testresults_query (From OE-Core rev: 9ce28f685e4282d81f179877cbafd0a52fa887bd) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26scripts: add new helper for regression report generationAlexis Lothoré
Add yocto-testresults-query script. This is a thin wrapper over resulttool which is able to translate tags or branch name to specific revisions, and then to work with those "guessed" revisions with resulttool (From OE-Core rev: b1460201b0f3d8fd7f977ac82f218bf9010d5573) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26scripts/resulttool/regression: add metadata filtering for oeselftestAlexis Lothoré
When generating regression reports, many false positive can be observed since some tests results are compared while the corresponding tests sets are not the same, as it can be seen for example for oeselftest tests (oeselftest is run multiple time but with different parameters, resulting in different tests sets) Add a filtering mechanism in resulttool regression module to enable a better matching between tests. The METADATA_MATCH_TABLE defines that when the TEST_TYPE is "oeselftest", then resulttool should filter pairs based on OESELFTEST_METADATA appended to test configuration. If metadata is absent from test results, in order to keep compatibility with older results, add a "guessing" mechanism to generate the missing OESELFTEST_METADATA. The guessed data is tightly coupled to the autobuilder configuration, where all oe-selftest executions are described (From OE-Core rev: 94ab7c2b892bf292dd86619ca9c63ddd7bf53f3c) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26scripts/resulttool/regression: remove unused importAlexis Lothoré
(From OE-Core rev: 4d6a74fcee1479562bf66360f20d528107c70887) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26scripts/oe-selftest: append metadata to tests resultsAlexis Lothoré
Many stored results TEST_TYPE are set to "oeselftest", however all those tests are not run with the same sets of parameters, so those tests results may not be comparable. Attach relevant parameters as tests metadata to allow identifying tests configuration so we can compare tests only when they are run with the same parameters. (From OE-Core rev: 406ec0a87e80d1ee0dd1d246adfe9507c10450ff) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26bitbake: documentation: bitbake: add file-checksums to varflags sectionRichard Elberger
Fixes [YOCTO #11605] by: - Adding definition of file-checksums to Variable Flags section. - Describe data to add to list which adds external file dependencies. - Write example on usage to prepend a value to file-checksums list. (Bitbake rev: 6bc65e6402a74c9a65e29333a7e0f1f85dcbcf58) Signed-off-by: Richard Elberger <rich@richelberger.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26bitbake: fetch/npmsw: add more short forms for git operationsMark Asselstine
>From the npm-install documentation [1] the CLI provides a set of short forms when the install fetches from git. These include "github:" example: npm install github:mygithubuser/myproject "gist:" example: npm install gist:101a11beef "gitlab:" example: npm install gitlab:mygitlabuser/myproject "bitbucket:" example: npm install bitbucket:mybitbucketuser/myproject Commit 1d8af6aed0a9 [fetch2: npmsw: Add support for github prefix in npm shrinkwrap version] by Stefan Herbrechtsmeier added support for the "github:" but the others would marked as 'Unsupported dependency'. The other prefixes are added in this commit, along with extending the tests to cover some of these. However, there is one more short form for github which npm-install allows which forgoes the prefix altogether. example: npm install mygithubuser/myproject Unfortunately this format is a bit problematic as it lacks any easily identifiable 'marker' to match against, and it could be either the github short form or install from folder format. Experimentation shows that the folder format requires a leading './' or '/', so we use this to rule out the ambiguity. If this approach to folder and github formats disambiguation is incorrect it won't matter anyways as the folder format is unrecognized by the code as-is and thus with this change or without, things would fail. Since we have to be less strict in the check for git operations we move it to be the last install format which we check, such that the less ambiguous formats can be sorted out first. [1] https://docs.npmjs.com/cli/v9/commands/npm-install [Yocto #14236] (Bitbake rev: 0ac6f6cb5d807919ed13a8b7bb3fb551b79c5a71) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26bitbake: gitsm: Fix path construction for relative submodule URIMike Crowe
The submodule repository URI contains a path to something not necessarily on the local filesystem. This means that we can't use realpath to normalise it without risking getting bad results if the path happens to match something on the local filesystem. This situation can cause very confusing errors if that matching local path happens to be a symlink to somewhere else. Using normpath rather than realpath means that the path simplification follows simple rules on the string rather than looking at the local filesystem and avoids problems. (Bitbake rev: 47b271e6c8d96960ebe70f80e58f30cc4cbf42e1) Signed-off-by: Mike Crowe <mac@mcrowe.com> Co-authored-by: Dave Craig Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26bitbake: utils: Use internal fetcher function to avoid duplicationRichard Purdie
We currently have two lists of "proxy" or "fetcher" environment exports. Make the one in utils match the one on the fetcher which has a more complete list of variables now. (Bitbake rev: f9165a798a307a6f0fee120d5c3de660d3a44ae8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26bitbake: fetch2/wget: Drop unused importRichard Purdie
This import is no longer used anywhere so can be removed. (Bitbake rev: 956128e394581855bf0d03b32a975dc91c2a7e0c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26bitbake: fetch2: Add GIT_CACHE_PATH and SSL_CERT_DIR into FETCH_EXPORT_VARSCaner Altinbasak
These environment variables are needed by gclient and needed to be passed into fetcher. (Bitbake rev: 9414ba62454c6b911addf6b0bc02af2afc69b926) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26oeqa/selftest/wic: Add test for uefi-kernel loaderPavel Zhukov
This is regression test for [1]. [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15033 (From OE-Core rev: d8ef15bb9ef652bf85002fe523ff5060b47bca6a) Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26wic: Fix populating of IMAGE_EFI_BOOT_FILES with uefi-kernelPavel Zhukov
wic plugin crashed if IMAGE_EFI_BOOT_FILES is not empty and uefi-kernel loader specified because of preliminary return from the function. [Yocto #15033] Fixes: | File "/mnt/builds/yocto/sources/scripts/lib/wic/plugins/source/bootimg-efi.py", line 371, in do_prepare_partition | for src_path, dst_path in cls.install_task: | ^^^^^^^^^^^^^^^^ | AttributeError: type object 'BootimgEFIPlugin' has no attribute 'install_task'. Did you mean: 'do_install_disk'? (From OE-Core rev: a6372f70f31b39ce9867b705d02205621d7a8685) Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26systemd: add group sgx to udev packagePeter Marko
>From NEWS for v250: * Device nodes for the Software Guard eXtension enclaves (sgx_vepc) are now also owned by the system group "sgx". >From NEWS for v248: * Intel SGX enclave device nodes (which expose a security feature of newer Intel CPUs) will now be owned by a new system group "sgx". Fixes following journal error entry during startup: /lib/udev/rules.d/50-udev-default.rules:43 Unknown group 'sgx', ignoring This is seen already on kirkstone. (From OE-Core rev: bab455cd9b1b82e778f8523a767eb281edf6689e) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26musl: Update to tip of trunkKhem Raj
This brings in following changes * 7d756e1c (upstream/master, origin/master) dns: prefer monotonic clock for timeouts * 07616721 fix return value of wcs{,n}cmp for extreme wchar_t values * 35fdfe62 math: fix undefined shift in logf * 7e13e5ae inet_pton: fix uninitialized memory use for IPv4-mapped IPv6 addresses * 7e6da7ac hsearch: fix null pointer arithmetic UB * f79b973d increase sendmsg internal buffer to support SCM_MAX_FD * 0ab97350 mq_notify: block all (application) signals in the worker thread * 711673ee mq_notify: join worker thread before returning in error path * 8c0c9c69 mq_notify: rework to fix use-after-close/double-close bugs * fde6891e mq_notify: use semaphore instead of barrier to sync args consumption * c3cd04fa fix pthread_detach inadvertently acting as cancellation point in race case * 115149c0 powerpc-sf longjmp clobbering of val argument * 5763f003 riscv64: add vfork * 269d1938 fix wrong sigaction syscall ABI on mips*, or1k, microblaze, riscv64 * ea3b40a3 fix integer overflow in WIFSTOPPED macro * f897461d fix debugger tracking of shared libraries on mips with PIE main program * a4b0a665 expose memmem under baseline POSIX feature profile * 9532ae13 use libc-internal malloc for pthread_atfork * 7d358599 prevent invalid reads of nl_arg in printf_core * c5f4b2df elf.h: add ELFCOMPRESS_ZSTD * 159d1f6c semaphores: fix missed wakes from ABA bug in waiter count logic (From OE-Core rev: 7379412a2ce7fe24943c858755f058dc2a15a081) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26systemd: add user for systemd-oomd if enabledLuca Boccassi
systemd-oomd.service has: User=systemd-oom So we need to create a static user for it, if its packageconfig is enabled. (From OE-Core rev: 1586edc919326cdbb412feafb9cde2cb15e419cb) Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26ffmpeg: fix build failure when vulkan is enabledDmitry Baryshkov
The patch fixes the following errors observed when building ffmpeg in vulkan-enabled distros: | src/libavutil/hwcontext_vulkan.c:363:7: error: 'VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME' undeclared here (not in a function); did you mean 'VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME'? | 363 | { VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME, FF_VK_EXT_NO_FLAG }, | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME | src/libavutil/hwcontext_vulkan.c:364:7: error: 'VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME' undeclared here (not in a function); did you mean 'VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME'? | 364 | { VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME, FF_VK_EXT_NO_FLAG }, | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME (From OE-Core rev: b16c8696be9d56edb5ff77210abfff9a784fad89) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-26docbook-xml: Switch from debian packages to upstream docbook sourcesRichard Elberger
This patch changes the docbook-xml distribution package source from debian to docbook which aligns the recipe with the source originator. Other changes made to the recipe include: This patch resolves [YOCTO #13270]. - removal of version 4.0 given docbook no longer distributes version 4.0 - simplification of the header description. - inline comments to communicate the rationale behind gathering multiple versions and LICENSE file handling. - minor ordering changes to align with styling conventions and better context to better communicate use - Added comment about magic XMLCATALOGS variable. This variable and subsequent inherit might be better placed in recipes that depend on docbook-xml but leave it for now to not cause a patch landslide. - Modify the related docbook-xml patch to remove docbook-xml-4.0 since it is no longer provided. - Put BBCLASSEXTEND to end of recipe per RP note on convention (From OE-Core rev: fc4471019313d981f0c951220cc65e8374a7e8e6) Signed-off-by: Richard Elberger <rich@richelberger.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-25gcr: correctly configure vala against introspection dataAlexander Kanavin
GI_DATA_ENABLED is the right source for making that decision as it additionally factors in presence of qemu-usermode in MACHINE_FEATURES. (From OE-Core rev: b32bb078d73ab9fd636d059cf70b5530a2f94cb4) 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>
2023-02-24checklayer: check for patch file upstream statusChee Yang Lee
yocto-check-layer to check all .patch file in layer for Upstream-status and list down all .patch file without Upstream-Status. set this test as expected failure for now, so this wont fail the check layer while still able to capture any patches with malformed or missing Upstream-Status in report. [YOCTO #14642] (From OE-Core rev: 237c1b66e5014123c1e5c3e78f9ab0357bcd62dc) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24icecc: enable the network only when ICECC_DISABLED is not setJose Quaresma
Enabling the network uncondictional is not need for some use cases. Such use case is usefull to reuse the sstate-cache of the build and it requires the icecc inherit in all of the builds. The real control control of the icecc is in the variable ICECC_DISABLED so this patch change the logic to enable the network when the icecc is in use. (From OE-Core rev: 0fd3a9c13a30a67ccef6619627efd9613755a0c3) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24build-appliance-image: fix HOMEPAGETrevor Woerner
Update the HOMEPAGE metadata. (From OE-Core rev: c59d21360d86f4fb9793faf7501003e6f3c97956) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24dev-manual: new-recipe.rst: add references to subsections in Examples sectionMichael Opdenacker
Making it possible to jump right away to the desired example Rename a section title to make it more suitable for a link title. Using short references (`Section Name`_) instead of :ref:`dev-manual/new-recipe:Section Name`) as we are in the same document. (From yocto-docs rev: 4058998dbeba4262ccced8999be338c04c324b48) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24dev-manual: new-recipe.rst: add Meson example recipeMichael Opdenacker
(From yocto-docs rev: 30cded4e59020a98205877970c530de35da46a60) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: system-requirements.rst: update supported distrosMichael Opdenacker
Syncing with meta-yocto/meta-poky/conf/distro/poky.conf (From yocto-docs rev: c48256499bafcf57e8b40202fd2d10b28c15daf9) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Suggested-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24manuals: document COMMERCIAL_[AUDIO|VIDEO]_PLUGINS variablesMichael Opdenacker
- Add COMMERCIAL_[AUDIO|VIDEO]_PLUGINS variables to the variable index. - Clarify that these plugins are still open-source - Improve line width (From yocto-docs rev: 8b161faad6b698b33165f02e1f5e78a693c7817b) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: update DEV_PKG_DEPENDENCY in variablesFawzi KHABER
Since release 4.1, the variable DEV_PKG_DEPENDENCY sets RRECOMMENDS instead of RDEPENDS for the -dev package on the main package, this change fixes the documentation to match the actual state Reviewed-by: Yoann CONGAL <yoann.congal@smile.fr> (From yocto-docs rev: 0e0790e7bcf4ee2d31301b4351528eb124a1fe98) Signed-off-by: Fawzi KHABER <fawzi.khaber@smile.fr> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24dev-manual: sbom.rst: add link to FOSDEM 2023 videoMichael Opdenacker
(From yocto-docs rev: 05f3c98e83830ccdde4289727d0bab563b8ea900) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> CC: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: Fix invalid feature nameNiko Mauno
Replace the invalid feature name with correct one which helps to avoid following bitbake error ERROR: Nothing PROVIDES 'core-image-minimal' core-image-minimal was skipped: 'empty-root-passwd' in IMAGE_FEATURES (added via EXTRA_IMAGE_FEATURES) is not a valid image feature. (From yocto-docs rev: 1c7086a3eda6539f09cae8917ccace93b14f8e9c) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: document meson class and variablesMichael Opdenacker
(From yocto-docs rev: aacd49e5c72ac1506fc09790902c6047ccf26a02) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: classes.rst: improvements to cmake class documentationMichael Opdenacker
- Fix quoting for path to cmake modules - Document OECMAKE_GENERATOR variable - Style simplifications (From yocto-docs rev: ecdc1775e27717ec87442575f65b1f24ca2b0348) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24dev-manual: new-recipe.rst: restructure examplesMichael Opdenacker
To make it possible to add more examples (CMake, Meson, Go, Rust...) - Change section title names - Adjust paragraph line length - Have the Autotools example after the one with a custom Makefile, corresponding to an increasing level of complexity. - Clarify that GNU make and the Autotools are used to build the applications, not by these applications. (From yocto-docs rev: 6f313e673fe4d2878c8166619c27c4958af73615) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: classes.rst: add python-setuptools3_rust and python_pyo3 classesMichael Opdenacker
(From yocto-docs rev: 65d41f164354494dae52949ce0532fd855de16ec) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Alex Kiernan <alex.kiernan@gmail.com> Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24manuals: update patchwork instance URLMichael Opdenacker
https://patchwork.openembedded.org/ has been since long discontinued Also better to mention https://patchwork.yoctoproject.org/ than the patchwork home page. (From yocto-docs rev: 15e2f662c9c519f54cd2c8b99c817725ed4c357b) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reported-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24kernel-dev: harmonize example with ref-manualUlrich Ölmann
(From yocto-docs rev: 02e8a7e25eda462a5e244bd2bfb557554c1155fb) Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24ref-manual: refer to MACHINE variable instead of KMACHINEUlrich Ölmann
Although in the example case of a "raspberrypi2" the variable KMACHINE has the same value as MACHINE, only the latter is an allowed override. So do not set the reader on the wrong track. Suggested-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> (From yocto-docs rev: 565ebcfe3ed68a9ea036f11cddafb36023f72099) Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24kernel-dev,ref-manual: fix old override syntaxUlrich Ölmann
Additionally use more common syntax to indicate that an actual machine name is supposed to be filled in for a concrete use case as has been suggested by Peter Kjellerstedt (and particularly no KMACHINE). Furthermore add missing quotes in the reference manual. Suggested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> (From yocto-docs rev: b66c035970f860b65cf712285f2d5a023620e6c3) Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de> Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24bitbake: cooker: Fix memory resident cache invalidation issueRichard Purdie
We've been seeing weird PRServ failures on the autobuilder. These had one failure always followed by a second. Whilst I can't reproduce the first, if I made that test fail, I could reproduce the second with memory resident bitbake. This was with the tests: prservice.BitbakePrTests.test_import_export_replace_db and then prservice.BitbakePrTests.test_pr_service_deb_arch_dep which was giving a strange looking error: NOTE: Running task 1053 of 1055 (/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/recipes-devtools/m4/m4_1.4.19.bb:do_package_write_rpm) NOTE: Running task 1054 of 1055 (/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/recipes-devtools/m4/m4_1.4.19.bb:do_package_qa) ERROR: No such task: do_package_write_rpm ERROR: Task (/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/recipes-devtools/m4/m4_1.4.19.bb:do_package_write_rpm) failed with exit code '1' where the issue is that selftest.inc written by the test framework and containing PACKAGE_CLASSES = "package_deb" was being ignored. The issue is the cached_statements{} within BBHandler() is not being invalidated at the right time. This patch changes the code to ensure base configuration is not parsed until inotify updates have been processed. (Bitbake rev: cada37c6b9e5862ca2c5a54ad6fd1e1f1939cd9c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24bitbake: lib/bb/siggen: fix debug() callRoss Burton
Bitbake f68682 changed the logger's debug() method to be compatible with logging.debug(), but this caller was still using the old API where you can pass an integer as the first argument: WARNING: Invalid arguments in bbdebug: (1, 1, 'Found unihash[...]') Instead, call bbdebug() which has the priority argument. (Bitbake rev: 18d4f9e8387f7994cf6d46300e25dda1c3a593b2) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24oeqa/selftest/prservice: Improve debug output for failureRichard Purdie
We keep seeing this failure on the autobuilder but the output amounts to "False is not True". Improve the debug message on the chance it may make the issue clearer. (From OE-Core rev: d03f4cf19c2cc96e9d942252a451521dfec42ebc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24mc: set ac_cv_path_PERL_FOR_BUILDMingli Yu
After mc upgrade to 4.8.29, it introduces PERL_FOR_BUILD [1] and will result in the below build failure on some system when we build under a project with long path. | make[4]: Entering directory '/buildarea2/WTEST_Regression/Rerun/build_dir/02161802-multilib_pkgs_conflict/qemux86-64-standard-std-OE/build1/tmp-glibc/work/core2-64-wrs-linux/mc/4.8.29-r0/build/doc/hlp/es' make[4]: Nothing to be done for 'install-exec-am'. | ../../../src/man2hlp/man2hlp ../../../doc/man/es/mc.1 ../../../../mc-4.8.29/doc/hlp/es/xnc.hlp mc.hlp.es | ../../../src/man2hlp/man2hlp: line 32: use: command not found | ../../../src/man2hlp/man2hlp: line 33: use: command not found | ../../../src/man2hlp/man2hlp: line 36: syntax error near unexpected token `(' | ../../../src/man2hlp/man2hlp: line 36: `my %static = (' | make[4]: [Makefile:632: mc.hlp.es] Error 2 (ignored) $ head -n 5 tmp-glibc/work/core2-64-wrs-linux/mc/4.8.29-r0/build/src/man2hlp/man2hlp #! /buildarea2/WTEST_Regression/Rerun/build_dir/02161802-multilib_pkgs_conflict/qemux86-64-standard-std-OE/build1/tmp-glibc/hosttools/perl # # Man page to help file converter # Copyright (C) 1994, 1995, 1998, 2000, 2001, 2002, 2003, 2004, 2005, # 2007, 2010, 2011 It's beacause the shebang line exceeds 128 which is usually the max length. So set ac_cv_path_PERL_FOR_BUILD to fix the above issue and altogether to remove the build path issue. [1] https://github.com/MidnightCommander/mc/commit/6b67d231a2f447cf5f33180c618c2a67849e6d15 (From OE-Core rev: 33d91a2434eeb20076c8226340b224b1d606c40f) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24u-boot: Map arm64 into map for u-boot dts installationPavel Zhukov
While arm64 is a valid UBOOT_ARCH (according to mkimage -A) u-boot keeps arm64 specific dts under 'arch/arm' directory. As the result the recipe tries to install arch/arm64 (if UBOOT_DTB was specified) and fails with [1]. Remapping "arm64" to "arm" to fix this issue. [1] | install: cannot stat '.../u-boot/1_2023.01-r0/build/arch/arm64/dts/u-boot.dtb': No such file or directory (From OE-Core rev: 3ca99403d5f320c6d7ae59b107f3b3bf183b4089) Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24create.py: add command arg to add layer to bblayers.confPedro Baptista
Add command arg `--add-layer` which enables the create and add layer in a single step. (From OE-Core rev: f3be788a55a2dde1f627aa85b08dc3ffa55d751f) Signed-off-by: Pedro Baptista <pedro.miguel.baptista@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24weston: Add kiosk shellJoshua Watt
Adds support for the kiosk shell to weston. The Kiosk shell is designed to run a fullscreen application in a "kiosk" mode, but unlike the fullscreen shell the kiosk mode still provides traditional desktop protocols. (From OE-Core rev: da4d6547f312285b5e246d8f974d2de76294fef3) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-24python3-setuptools: upgrade 67.3.1 -> 67.3.3Wang Mingyu
Changelog: ========== #3820: Restore quoted #include argument to has_function. #3827: Improve deprecation warning message on pkg_resources.declare_namespace to display package name. (From OE-Core rev: de8e7e0c2cbd558678ee59fae8b0024c6d0a7b9a) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-19 22:21:12 +0000