summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2023-03-01python3-zipp: upgrade 3.14.0 -> 3.15.0Tim Orling
https://zipp.readthedocs.io/en/latest/history.html#v3-15-0 v3.15.0 (24 Feb 2023) * gh-102209: test_implied_dirs_performance now tests measures the time complexity experimentally. Reference: https://github.com/python/cpython/issues/102209 (From OE-Core rev: 1cb64a5b6a950eb7f7c72125c5741fdafe236f0b) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-01python3-more-itertools: upgrade 9.0.0 -> 9.1.0Tim Orling
Upstream docs currently have a typo showing the changes as 8.14.0 https://github.com/more-itertools/more-itertools/commit/89d58c2ec089f3df54ed6cc9279949b8e2bbcd29 9.1.0 ----- * New functions - iter_index() (from the Python itertools docs) - transpose() (from the Python itertools docs) - matmul() (from the Python itertools docs) - factor() (from the Python itertools docs) - gray_product() (thanks to haukex) * Changes to existing functions - sieve() was updated to match the Python itertools docs - maxsplit() was updated to fix a bug (thanks to abingham) - sliced() had its type hint updated (thanks to ad-chaos) * Other changes - The batched function is marked as deprecated and will be removed in a future major release. For Python 3.12 and above, use itertools.batched instead. (thanks to neutrinoceros) - The type hints now used postponed evaluation of annotations from PEP 563 (thanks to Isira-Seneviratne) - Some documentation issues were fixed (thanks to Voskov and jdkandersson) (From OE-Core rev: 436b92846406273fb3651f4f026e9fd3871ee71c) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-01kernel: Add kernel specific OBJDUMPKhem Raj
This helps in switching toolchains cleanly for kernel build between gcc and clang Currently, some kernels allow building with clang but not all the distro might use clang as default system compiler but kernel may demand gcc which is provided via KERNEL_* variables, however kernel does use OBJCOPY at places during build and it maybe set to use llvm objcopy when using clang. That should be a deliberate setting when clang is used for kernel as well, otherwise it should use binutils provided objcopy (From OE-Core rev: 17b409f2fd97894e0943d13c2cb0d52abde647e3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-01libsdl2: add missing libdecor RDEPENDMarkus Volk
libdecor is dlopen'ed ... add it as RDEPEND to make it work on runtime (From OE-Core rev: 321f0819515cd53362b1b84aa2d1eece75e013e5) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-01diffoscope: upgrade 235 -> 236Wang Mingyu
(From OE-Core rev: f2a7a4a899dff74b88c4192f1d97a14833016029) 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>
2023-03-01gpgme: fix python setuptools invalid version issueChen Qi
The python3-gpg's version is now '1.18.0-unknown'. Such version has been treated as invalid for setuptools >=66.0.0. The error message is as below: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '1.18.0-unknown' (package: gpg) Fix this issue by removing the '-unknown' suffix. (From OE-Core rev: 3a8bf81c5fb6111eab9784192754271efc85ee5c) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-01nghttp2: Deleted the entries for -client and -server, and removed a ↵leimaohui
dependency on them from the main package. By default there is nothing in nghttp2-client and nghttp2-server ,nghttp2-client and nghttp2-server aren't created. So there are dependences error if install main package. Problem: conflicting requests - nothing provides nghttp2-client >= 1.52.0 needed by nghttp2-1.52.0-r0.core2_64 - nothing provides nghttp2-server >= 1.52.0 needed by nghttp2-1.52.0-r0.core2_64 (From OE-Core rev: d2cbe060955c598bd81923ecd554fbe82c17af99) Signed-off-by: Lei Maohui <leimaohui@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-01gnutls: Updated ther patch which fixes build error for fips enabled.leimaohui
The context of lib/Makefile.am in gnutls_3.8.0 has changed when updated from gnutls_3.7.8. (From OE-Core rev: 7c00bf8e0a0f9c88de6cf782b7fa3db7872c4100) Signed-off-by: Lei Maohui <leimaohui@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28systemd-systemctl: Create machine-id with "uninitialized" text in itMarek Vasut
Instead of creating empty /etc/machine-id file using touch, write text "uninitialized" into it. Systemd requires "uninitialized" in the /etc/machine-id file to trigger systemd-firstboot . (From OE-Core rev: 263c852269027b1bd311e116021ac49d9001e1b0) Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28oeqa/selftest/resulttool: add test for metadata filtering on regressionAlexis Lothoré
Multiple filters have been added to resulttool to ensure that test results are compared only to relevant older tests results Add some unit tests about added filters: - tests should only be compared when machine matches - tests run as oeselftest should only be compared when OESELFTEST_METADATA matches - many ptests should match despite non-static names - runtime tests should match with matching tests regarding ltp tests content (From OE-Core rev: b84302ef56f2516742a496aef43b89d4c3decd37) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28scripts/yoct_testresults_query: manage base/target revision not foundAlexis Lothoré
If yocto_testresults_query.py is run from oe-core instead of poky, the script will very likely fail since poky tags do no exist in oe-core. If one or both revisions are not found, log the error and a suggestion about the reason (the script being run in oe-core instead of poky) (From OE-Core rev: 758ac050ffd91524d400c196865b1ed27ece8776) Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28glibc: remove obsolete CVE ignoresRoss Burton
Remove some obsolete CVE ignores now that releases have been made, CPEs updated, or upgrades done: CVE-2020-10029 is marked as fixed in 2.32. CVE-2021-27645 is marked as fixed in 2.34. CVE-2022-39046 is marked as fixed in 2.37. (From OE-Core rev: a383d0e726011007419dd102cd6484733d80d9f6) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28glibc: add ignore for CVE-2023-25139Ross Burton
This CVE has been fixed in the 2.37 release branch (07b9521fc6) and we're now using a SHA that incorporates that commit, so manually mark it as ignored. (From OE-Core rev: b143e355ef362dac89f8b125904d2e47c74e597e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28cve-extra-exclusions: ignore inapplicable linux-yocto CVEsGeoffrey GIRY
Multiple CVE are patched in kernel but appears as active because the NVD database is not up to date. CVE are ignored if and only if all versions of kernel used by master are patched. Also ignore CVEs with wrong CPE (applied to kernel but actually are for another package) (From OE-Core rev: 92770a08c04a6c1eb351231d937b16e76558f013) Signed-off-by: Geoffrey GIRY <geoffrey.giry@smile.fr> Reviewed-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-28VOLATILE_TMP_DIR: addTrevor Woerner
Provide a mechanism to allow users to choose whether the /tmp directory is on persistent storage (non-volatile) or a RAM-based tmpfs (volatile). The default is volatile. Works for both sysvinit-based and systemd-based systems. (From OE-Core rev: 8b76c0637eaeaf5bd5e696680cd74b7a642f4157) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-27quilt: run tests as ptest user, and let that user write into the testsRoss Burton
The tests need to run as a non-root user, but that user also needs to be able to write into the tests directory to create the work directories. Use the new ptest user that ptest-runner creates to avoid having to add a new user, and ensure that the test/ directory is owned by the ptest group and that group has write access. This solves the ptest regression where since oe-core 9a287b4 no quilt tests were actually running. A better solution would be to allow the tests to create a work directory in another directory, but that would need work upstream which can happen later. (From OE-Core rev: 70dc9c114283cde18771287fb17fcebc537e7387) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-27meta-selftest/files: add ptest to static-passwd/-groupRoss Burton
As ptest-runner creates a new user, we need to add it to the testing static passwd file. (From OE-Core rev: 009726f04c000cc50ce44305669bd8e940e64a9c) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-27ptest-runner: add non-root ptest user for tests to run asRoss Burton
Some tests really don't want to be run as root, either because they expect to get "permission denied" errors occasionally, or have explicit checks. Instead of numerous recipes re-inventing user creation in run-ptest, create a user in the ptest-runner recipe that they can all use. (From OE-Core rev: d58cf08421e0f89840820370dd3c5b6e153efcbb) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-24 18:54:02 +0000