summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: cooker/command: Add a dummy event for tinfoil testingRichard Purdie2021-09-262-0/+15
| | | | | | | | | | We need a command genetating an event to test through the tinfoil API. The current test has IO load issues so add a dummy version which won't have the IO constraints. (Bitbake rev: a144178584394ea0700ffc2f2bfac94e8690effc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: siggen: Fix sorting in diff outputRichard Purdie2021-09-261-7/+7
| | | | | | | | | The diff output isn't deterministic at the moment as the sets can have differing ordering. Sort the output so it is consistent. (Bitbake rev: 117830c1d7ef3e53052fa326e1ca62c5c3946c45) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-worker: Allow shutdown/database flush of pseudo server at ↵Richard Purdie2021-09-261-1/+9
| | | | | | | | | | | | | | | | | | task exit We have a problem where pseudo server processes exist after bitbake exits and hold the pseudo database in memory. In a docker container, the processes will be killed as the container is destroyed with no warning and no opportunity to write the data to disk. This leads to permissions/inode corruptions and data loss. Send a shutdown message to pseudo which in new versions of pseudo will flush the database, thereby fixing some of the issues people using docker containers see. (Bitbake rev: a07a971b40acd3eee12e203d2cfa3e49f56109f6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp/5.13: drop recipesBruce Ashfield2021-09-261-23/+0
| | | | | | | | | | 5.13 has been removed from core, and we've moved the default support to 5.14, so we can drop our bbappend. (From meta-yocto rev: 5cb9ef98c90321ae5d57123d82b68f14e6c85f39) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-tools-profile: Exclude systemtap from riscv32 as wellRichard Purdie2021-09-261-0/+1
| | | | | | | | The recipe can't be built for riscv32 so exclude it alongside riscv64. (From OE-Core rev: 61feb650ac450db0a30675fc40bb65fab773159a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools.bbclass: use ordinary append for file-checksums updateMatt Madison2021-09-261-4/+1
| | | | | | | | | | | | | | | | Commit 29daffc2410f06f36b779d5bf1fd1ef6e900ca8f added an anonymous python function to append the site file dependencies for do_configure. This causes any recipe that inherits allarch after autotools to end up with a different set of file checksums for each machine, since the anonymous python would get processed before the TARGET_ARCH changes in allarch. Use an ordinary += assignment to fix this. (From OE-Core rev: 60af398f520c938600205ef40e27f90e5342209c) Signed-off-by: Matt Madison <matt@madison.systems> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Add in ability to flush database with shutdown requestRichard Purdie2021-09-261-1/+1
| | | | | | | | | | Pulls in: pseudo_db: Flush DB if there is a shutdown request fcntl: Add support for fcntl F_GETPIPE_SZ and F_SETPIPE_SZ (test fix) (From OE-Core rev: 0882095d608ce3abbcc9814517434c21ea549063) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/qemurunner: Use oe._exit(), not sys.exit()Richard Purdie2021-09-261-1/+1
| | | | | | | | | sys.exit will cause finally statements and other code to run at exit. Since we're using os.fork() here, os._exit() is apprioriate in this codepath. (From OE-Core rev: ec08498ff29de9ccd23be88b9d7af3dab6bbb81e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libsamplerate0: Set correct soname for 0.1.9Tom Pollard2021-09-262-0/+14
| | | | | | | | | | Manually patch SHARED_VERSION_INFO, which was missed in the 0.1.9 release and later incorrectly fixed until 0.2.1 (From OE-Core rev: cb2e8efd316d44b9b1453882114856e0eb7b3500) Signed-off-by: Tom Pollard <tom.pollard@codethink.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bzip2: Update soname for libbz2 1.0.8Tom Pollard2021-09-261-1/+1
| | | | | | | | | | Set shared library name as libbz2.so.1.0.8, version in configure.ac already synced via do_configure PV substitution. (From OE-Core rev: 07e3abc9d282a54add69a6905ec4248f3104219f) Signed-off-by: Tom Pollard <tom.pollard@codethink.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/5.13: drop recipesBruce Ashfield2021-09-263-145/+0
| | | | | | | | | | | | 5.13 is EOL upstream, and we've moved to 5.14 for the release, so we drop the versioned recipes. The kernel tree and branches will stay available for use, but other layers must create recipes if they wish to continue with 5.13. (From OE-Core rev: b08456824ce5d8701ddd2db0be3f8f2f4894853c) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: fix build against 5.15+Bruce Ashfield2021-09-263-1/+1227
| | | | | | | | | | | | When testing linux-yocto-dev 5.15-rc, lttng-modules fails to build. Upstream already has fixes for 5.15 in the release branch, so we backport the two patches here and we can drop them on the next version bump. (From OE-Core rev: af17b507009be14d6f7069d39feb1fbd7563471d) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules/dev-upstream: update to 2.13-latestBruce Ashfield2021-09-261-2/+2
| | | | | | | | | | | To ensure we can build against 5.15, and to keep in sync with the versioned recipe, we bump to the latest commit on the 2.13 release branch. (From OE-Core rev: 1317bd6f92f32444301c5f6cf0c98e7a64e92f66) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-dev: update to v5.15-rcXBruce Ashfield2021-09-261-1/+1
| | | | | | | | | | The main reference kernel has moved to 5.14, so we bump -dev to 5.15 for the release. (From OE-Core rev: 36e3ae14af7df8584063e5aac4fa32a57542c3a3) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ffmpeg: fix CVE-2021-38171Kiran Surendran2021-09-262-1/+44
| | | | | | | | | backport from upstream (From OE-Core rev: 3cb40cabc79e4c9b4ffaf99543368b0c57d18df1) Signed-off-by: Kiran Surendran <kiran.surendran@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* inetutils: fix CVE-2021-40491Yi Zhao2021-09-262-0/+89
| | | | | | | | | | | | | | | | | | CVE-2021-40491: The ftp client in GNU Inetutils before 2.2 does not validate addresses returned by PASV/LSPV responses to make sure they match the server address. This is similar to CVE-2020-8284 for curl. References: https://nvd.nist.gov/vuln/detail/CVE-2021-40491 Patch from: https://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=58cb043b190fd04effdaea7c9403416b436e50dd (From OE-Core rev: 1b857807f1cf8fee3175f8479a0c7cb1850bd9a9) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto-bsp: Update the default kernel to v5.14Kevin Hao2021-09-244-3/+26
| | | | | | | | | | Introduce the bbappend for v5.14 and also set the default kernel to v5.14 for all the boards. (From meta-yocto rev: bed70a64b5b772fd71a7ff88a9f3719082e9398c) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: set default kernel to 5.14Bruce Ashfield2021-09-242-3/+3
| | | | | | | | | | both -rt and -standard have been updated to 5.14, so we switch out defaults. (From meta-yocto rev: 952a771f5707d9e84beee6195b7a3cfb3a930702) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine: bump qemu preferred versions to 5.14Bruce Ashfield2021-09-242-2/+2
| | | | | | | | | | 5.14 is the latest reference kernel, so let's make it the default. (From OE-Core rev: af19c44c4af68568de2ddb5c11d8ad34ac600522) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: update to 4.5-latestBruce Ashfield2021-09-242-28/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To fix issues with 5.14+ kernels, we bump to the latest 4.5 systemtap. This means that we can drop a backported patch, and we pickup the following changes: 7f6992539 Correct RISC-V handling of SDT markers and document their format. 2dfd140fd Fix races in perf probe task finder callback f463f6053 The /* pc=0x... */ is no longer printed by "stap -v -L 'kernel.function("*")' 0bd97a806 Use task_state tapset function to avoid task_struct changes 4996a29c6 tapset: start adopting kernel netif_* tracepoints in netdev.* tapset fb0851e62 dwflpp.h: add conditional EM_RISCV define c5599df8e Add dwarfless register access for RISC-V 33d861435 Add bactrace support for RISC-V 2ae3fc866 RISC-V dwarf register number to pt_reg mappings 3df603720 Eliminate the sa_restorer field in sigaction struct for RISC-V. a6aff9d33 Avoid generating problematic asynchronous unwind tables on RISC-V a463860c3 Add RISC-V 64-bit processor support 8486fd78d Add the actual RISC-V syscall-number mappings to the tapsets. 1e383aa38 Add creation of mappings between syscall names and numbers for RISC-V aedb2dbe7 RISC-V doesn't have crash available, disable it for rpmbuilds. 33a9bf1a1 Update to newer config.guess to support RISC-V 3bca17469 Use lex_cast instead of to_string when shortening function names. 0b5bc934a Revert "runtime: unregister the control channel before cleaning up" 166a95089 runtime: fix panics when polling on the control channel while unloading e6a1b008b Shorten function names that will exceed the kernel's objtool limit of 128 4f54ba033 runtime/transport: add a comment blurb for ordering invariant at shutdown dbe08f1ac runtime: unregister the control channel before cleaning up 798a67290 bpf pr23478 :: test non-unique key/val iteration 079f5d708 bpf pr23478 :: test multi-key associative array iteration 70b24879d rhbz1938312: un-disable bpf.exp after kernel bugfix 2896d6f5a pr23478 WIP: fixes for existing foreach testcases 0d1a38dbc pr23478 WIP: rework bpf foreach to handle multi-key array 14a2c8f54 Run task_fd_lookup.exp with --compatible 4.0 f2c147767 PR28184: Adapt to kernel rename __fcheck_files to files_lookup_fd_raw 0581a6560 PR28184: Adapt to kernel rename __fcheck_files to files_lookup_fd_raw 559fd51fe testsuite: time-limit auxiliary child processes 5d89bb03e stapbpf bugfix: missing in_block() in try-catch code 04b43f48f releng: ditch custom pie/ssp CFLAGS engine in configure.ac b47d03c20 PR28079: Adapt to kernel 5.14 task_struct.__state change e66f3a83b runtime: adapt to -Werror=implicit-fallthrough=5, dyninst runtime ea00c1070 PR28140: kernel 5.14-rc adaptation, jump_label_patch ffb0a38ea runtime: adapt to -Werror=implicit-fallthrough=5 efba2178f Revert to using test_tsk_thread_flag for uprobes2 23db8b29f PR27984: Adjust the address so dwfl_module_addrinfo finds correct function name a29f65d57 PR28079: Adapt to kernel 5.14 task_struct.__state change 2f7e966c0 testsuite item typo fix 5abb4d130 PR27934: give fuller diagnosis for pass-5 probe-registration errors 371805aa0 PR27820 tapset/bpf/logging.stp: implement abort() tapset function ee361f183 PR27820 tapset/bpf/logging.stp: move bpf versions of functions 968173f7f runtime: linux 5.14 compat: <linux/panic_notifier.h> ef5a8b9ed runtime: fix unintended compile error with autoconf-x86-uniregs.c 84ef6bd9f Revert "systemtap.spec: don't buildrequire emacs" 65fc44163 spin-rawhide: ok tweak the git-archive top level path too c7f1c12e1 spin-rawhide: switch to ~ versioning for Source: file names too bff2b2ff5 spin-rawhide: switch to ~ versioning for n-v-r 7c2751e37 task_finder_vma: add autoconf check for hlist_add_tail_rcu() ea7c27bbe Don't fail vma tracking mmap callback if module is already known. 2eb7fdfdb Use the path instead of the module for vma tracking mmap callback. a5104a612 update READMEs + man pages for freenode -> oftc move 23c351645 Update list of reasons for latencytap.stp example 5409ddea1 rhbz1972805: add basic syscall-in-ptregs support for s390x 0fc73fc4e systemtap.spec: don't Require: libvirt 515a6a2d6 rhbz1972828: tapsets: iommu tracepoints eaf63df6a ppc64 runtime: FULL_REGS() gone 757d4f654 c++ buildability: util.cxx - unique_ptr 1a6e7aea7 systemtap.spec: don't buildrequire emacs 5ff28c970 Allow for adjacent segments belonging to different modules. b1e8cd5de Note that Python is a requirement. 27115ab4c Get the enumerator's enumeration type 1288bee31 testsuite/systemtap.base/perf.sh drop bashism 4755bc453 Add hlist macros for use by hlist_add_tail_rcu bccf5123f parse.cxx: Initialize functioncall synthetic field 9bbee6518 Add hlist_add_tail_rcu for rhel 6. 630e406b8 Don't assume ISO C99 4a3ad3532 Extend vma mapped entries when the address is adjacent. 294b7a53e stap-prep: switch to using main vmlinuz file as debuginfod test download 643351d22 PR27903: grok more glibc dwarf 3a843482a c++11 hygiene: use cxx_override macro for pre-4.7 g++ 3e9bcd7b1 Fix more -Wformat-nonliteral and -Wmismatched-tags when compiling with clang 8e5145ae4 dtrace: Use -o option to specify output file for CPP b3a392975 Fix -Wformat-nonliteral and -Wformat warnings with clang 545535f82 Fix -Woverloaded-virtual warnings when building with clang 0f4bd3219 set2: Return this from assignment operator 6de815bca Add missing copy constructors to set1_ref and set1_const_ref 930b54119 Add some override specifiers where missing 14f04522b util.cxx: Use abs() instead of labs() 13016e9dd systemtap.spec: python3 tweaks 494ece199 PR27864: tolerate loc_unavailable during loc2c transform e8f5c058f autoconf: version bumps for the next release-4.6 77abac91d version bumps for the next release-4.6 0eba8a46b NEWS: release-4.5 (From OE-Core rev: aa27c2e7570f229bf82f18cf07aae93ba96ca9f6) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: introduce 5.14 reference kernelBruce Ashfield2021-09-243-0/+145
| | | | | | | | | | | | | | | | | | Each release of the kernel is not typically used as a versioned reference kernel, but since 5.13 has gone EOL upstream and was never part of a release, we take the opportunity to udpate our reference to 5.14. 5.13 will be removed in subsequent commits, once all dependent BSPs and layers have been updated. No issues were found across all architectures, images in qemu boot testing. (From OE-Core rev: 634760461542a14bbf3625ff12393dc7428f6001) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-headers: bump to v5.14Bruce Ashfield2021-09-242-3/+5
| | | | | | | | | | | | The reference kernel is moving to 5.14, and 5.13 is EOL upstream, so we update the libc-headers to match. No patch issues were found for musl or glibc. (From OE-Core rev: 3cdaf2cb64303bc58ab8be40fce4091b5a7809b4) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: fix do_compile error when PACKAGECONFIG examples is enabledChangqing Li2021-09-232-0/+36
| | | | | | | | | | | | when PACKAGECONFIG enabled examples, compile failed with error: fix below compile error during PACKGAGECONFIG examples is enabled: tmp/work/corei7-64-wrs-linux/lttng-ust/2_2.13.0-r0/recipe-sysroot-native/usr/bin/x86_64-wrs-linux/../../libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/11.2.0/ld: warning: liblttng-ust-common.so.1, needed by ../../../src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link) tmp/work/corei7-64-wrs-linux/lttng-ust/2_2.13.0-r0/recipe-sysroot-native/usr/bin/x86_64-wrs-linux/../../libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/11.2.0/ld: warning: liblttng-ust-tracepoint.so.1, needed by ../../../src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link) (From OE-Core rev: 907ebb5bb3d44dd5f68deb238098fb6f6413e2d4) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: Add tests for bitbake shell/python task outputRichard Purdie2021-09-232-0/+128
| | | | | | | | | | We've seen issues where shell/python tasks lose their log file entries or output and also where output is duplicated. Add some tests to attempt to spot regressions in this area in future. (From OE-Core rev: 414020a9bd656ee61efe2f47db1b31d86b15c1c8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Fix log flushing raceRichard Purdie2021-09-231-38/+38
| | | | | | | | | | | | | | There is a race between sending the TaskFailed event which could trigger the UI to look at the logs and flushing and closing the log files. Reverse the order of the finally clause and the exception handling to ensure we've handled the logfiles before sending the task events. This should fix a race seen in bblogging.BitBakeLogging.test_python_exit_logging (Bitbake rev: 032190aac31604d37740d8aecf6e74a5448de358) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Make exception printing clearerRichard Purdie2021-09-231-1/+1
| | | | | | | | | | | | | | Shows: ERROR: SystemExit(1) instead of: ERROR: 1 (Bitbake rev: df89e37c33e4398a5f8ece9a8b973be3fe2ff361) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Ensure python stdout/stderr is logged correctlyRichard Purdie2021-09-231-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Currently we see things like: Log data follows: | DEBUG: Executing python function do_pythontest_exit | DEBUG: Python function do_pythontest_exit finished | ERROR: 1 | This is python stdout Whilst after the change we see things like: Log data follows: | DEBUG: Executing python function do_pythontest_exit | This is python stdout | DEBUG: Python function do_pythontest_exit finished | ERROR: 1 since the output is now correctly mixed with the log messages. In some cases the logging tests indicate the output is being lost entirely which is bad for debugging and makes things rather confusing. (Bitbake rev: 8966b43761500e0505333d8c9a3f0f2c3dbe7559) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ssate: Cleanup directtasks handlingRichard Purdie2021-09-231-14/+4
| | | | | | | | | | | | | There are several tasks which should only be triggered by direct dependencies. Some are listed in the dep loop, some are not. They should all be in both cases. Fix this by making a list and using the list in both cases to fix various inconsistencies. (From OE-Core rev: 29d285bc07bd7732c7ea39c0fd03c0b3c0d93e52) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Avoid deploy_source_date_epoch sstate when unneededRichard Purdie2021-09-231-0/+4
| | | | | | | | | | | | This sstate task is only needed when depended upon, it can be skipped if there are no tasks running that directly depend upon it. This reduced the number of sstate tasks in something like an image build. (From OE-Core rev: 601cee016da5c7505915e26641a085714de175ce) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure deploy tasks don't pull in toolchainsRichard Purdie2021-09-231-2/+2
| | | | | | | | | | | | | | If an image is built from sstate, the cross toolchain was being pulled in. This was due to the sstate dependencies for deploy tasks not being considered in the "depvalid" logic. do_deploy tasks do not need their populate_sysroot dependencies when installed from sstate so skip these. This reduces the sstate pulled in by an image build from sstate significantly. (From OE-Core rev: 8047c184f8266fc047c0e5a5524586d414528626) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Mark deploy an sstate taskRichard Purdie2021-09-231-0/+1
| | | | | | | | | | | | | | Deploy is a tricky task as it isn't in SSTATETASKS as it isn't always present. We do need to ensure dependency chains around do_deploy tasks are correctly handled as sstate tasks though. For now add to the list of sstate tasks manually (like the other locale task reference). Without this, missing manifest files could be reported now that do_deploy tasks no longer have their dependencies added by the depvalid function. (From OE-Core rev: 1fdbe550323b98ca67ed7130f5a0d7d626bd2c64) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Drop useless classRichard Purdie2021-09-233-9/+1
| | | | | | | | | | | | | | | This class was added by me back in 2007 and has changed one for a whitespace issue since. It only has two lines and neither are particularly useful, one was replaced by the nopackages class, the other adding recursive dependencies also is now mainly problematic adding tons of unneeded dependencies. The name is hard to understand and the class doesn't have a clear purpose. Drop it. Remove the references in devtool (which may be the one reason to keep it around but in my view still not worth it). (From OE-Core rev: 6e2cbfc561dac89bf9183d24d90e52f7d9117826) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball/uninative-tarball/meta-ide-support: Drop useless meta classRichard Purdie2021-09-234-4/+1
| | | | | | | | | | | | The class adds an emtpy PACKAGES setting but most code now uses the nopackages class which is much clearer. It also adds recursive do_build dependencies which don't really serve any useful purpose any more. Simplify the code and drop the class use. (From OE-Core rev: 030d56e2e8ece93472adc51fe467221d846c9ac0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base/images: Drop use of 'meta' class and hence do_build ↵Richard Purdie2021-09-231-1/+3
| | | | | | | | | | | | | | | | | | | dependencies The 'meta' is old and not very useful. It empties PACKAGES and creates recursive do_build dependencies. We shouldn't need such recursive build dependencies any more so simplify the code. This does cause behaviour changes as some dependencies are no longer built. It did show up issues with qemu-helper-native handling for example but those issues look like real races and the underlying dependency chains were not correct. 'bitbake XXX --runall build' would give the previous behaviour. (From OE-Core rev: 41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* reproducible_build/package_XXX: Ensure SDE task is in dependency chainRichard Purdie2021-09-234-3/+8
| | | | | | (From OE-Core rev: 938e4dfb68a465f61cb754b2cd28d0728616b5a9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_ipk/deb/rpm: Drop recursive do_build task dependenciesRichard Purdie2021-09-233-10/+3
| | | | | | | | | | | | | | | | | | | | | | | | | This is a controversial change which removes the recursive dependencies from the do_build target of packaging tasks of recipes. Currently this means when you "bitbake <image>" or "bitbake <recipe>", the packaging tasks run for all packaging backends enabled for all recipes in the dependency chain. The same therefore then applies to images. We don't actually need that, it is a convinience thing. Removing it massively simplifies the task graph and causes much fewer tasks to execute in many common scenarios. It also means less sstate is fetched for example when building an image. This means when building a recipe all package formats would be built but when building an image, only the format used by the image would be generated. This should be an improvement in most cases but some CI systems may need to be explict about what they're building. 'bitbake XXX --runall build' would give the previous behaviour. (From OE-Core rev: 220d29a5abb5be8b80c64d8f2f48949bc8c534a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siteinfo/autotools: Ensure task checksums reflect site filesRichard Purdie2021-09-235-9/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, if you change the site files, nothing rebuilds since they are not accounted for in task checksums. They could/should be through the file-checksums task flag. We need to cache all the files looked for, whether the exist or not so that if they do exist and didn't, the checksum also changes. This gets complicated by the need to clean out hardcoded build paths from the variable and that other layers can have site files. This patch adds this functionality. A new variable, SITEINFO_PATHVARS is added which controls which substitutions to make on the file-checksum values to remove the hardcoded paths. Layers adding site files will need to set this to a variable that has the layer path in it and is excluded from task hashes (COREBASE is the one the core layer uses). This patch will cause yocto-check-layer to fail for some layers where site files are added yet the layer isn't a machine specific layer. This is arguable correct since these additional site files apply to all recipes and things from a layer like core could be changed by such changes so it is right they should rebuild. There is a determinism issue potentially there if not. meta-openembedded does have some such references but looking at them they should move to core or likely just be removed as most look obsolete anyway. [YOCTO #13729] (From OE-Core rev: 29daffc2410f06f36b779d5bf1fd1ef6e900ca8f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/qemu: Add explict depends for qemu-helper addto_recipe_sysroot taskRichard Purdie2021-09-232-2/+5
| | | | | | | | | | The populate_sysroot task isn't enough for qemu-helper-native, we need it's addto_recipe_sysroot task. This corrects what amounts to bad dependency information to be explicit. (From OE-Core rev: 55623420208bc4c77a61492d2bbcbc71d3123acd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site: Drop ORBit2 relared cached variablesKhem Raj2021-09-238-113/+0
| | | | | | | | | ORBit2 is long gone (From OE-Core rev: a5c5dd9229553e0e364f083d661382fe0c15600c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site: Drop caching libIDL_cv_long_long_formatKhem Raj2021-09-2314-42/+0
| | | | | | | | | recipe for libidl has long been deleted (From OE-Core rev: 587d0b51b09cd426dc4b2b7646fa063d10ae4f2f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: add CVE_PRODUCTSteve Sakoman2021-09-231-0/+2
| | | | | | | | | Upstream database uses both "connman" and "connection_manager" to report CVEs (From OE-Core rev: eadf7bb17289731be9747822e3d4084ab69cf109) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-publish-sdk: Disable git gc to avoid build errorsRichard Purdie2021-09-231-2/+2
| | | | | | | | | | I've puzzled over why I see local eSDK test failures. It is due to having a messy git tree locally, git then runs git gc in the background which races against the deletion code for the publish test. Disable git gc to avoid this. (From OE-Core rev: d938a74097202396beda2e3bb4f582342d6dfa1b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests/fetch2: Use our own git server for dtc test repoRichard Purdie2021-09-221-1/+1
| | | | | | (Bitbake rev: 36f6dce1b21a7d9f39a73f081395c71045960318) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/target/ssh: don't assume target_dumper is setRoss Burton2021-09-211-1/+3
| | | | | | | | | | The target_dumper property is only set by the QemuTarget subclass, so assign a default value and check it isn't None before calling it. (From OE-Core rev: add36cf85380bf7dc5339a9d65f951923317440b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pybootchart: Avoid divide by zeroRichard Purdie2021-09-211-1/+4
| | | | | | | | | | Avoid a rare divide by zero error if there isn't data point spread. [YOCTO #14547] (From OE-Core rev: d7e36d01e87ddf89f76f164a0b7d98f597a53fa5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libsoup-2.4: remove obsolete intltool dependencyRoss Burton2021-09-211-1/+1
| | | | | | | | | This hasn't been needed since libsoup 2.65.2. (From OE-Core rev: 250a3f9a804917c8a9427d0209365d27b1b8fa4a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shared-mime-info: use a more concise descriptionRoss Burton2021-09-211-1/+1
| | | | | | | | | For example we don't need to talk about historic build dependencies. (From OE-Core rev: b67ae98ef803b889fceb5713c539504d48f1a926) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross: Drop unused do_installRichard Purdie2021-09-211-4/+0
| | | | | | | | | | | | | All the users of the cross class I could find redefine the do_install function. It is unusual and likely undesirable for the class to be changing this from the default and likely a leftover from different times. Remove it as it isn't doing anything. [YOCTO #9272] (From OE-Core rev: 72f0e03a6909e6856510d913863fc9301de32cec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: remove obsolete intltool-native dependencyRoss Burton2021-09-211-1/+1
| | | | | | | | | intltool was replaced with gettext in the 0.8 release. (From OE-Core rev: 0438c8e73419c0a81bbb42f777eb3e36f4878e79) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: remove aarch64 xorg exclusionJon Mason2021-09-211-2/+0
| | | | | | | | | | aarch64/qemuarm64 has had graphics support for some time. Remove this exclusion and allow graphics tests to be against qemuarm64. (From OE-Core rev: 1b436e4894663fa76865636b0b41c0c1503cc3bf) Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 08:46:52 +0000