Mirror of git.yoctoproject.org/meta-virtualization https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=styhead 2022-02-18T18:07:10+00:00 2022-02-18T18:07:10+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2022-02-18T18:05:37+00:00 urn:sha1:108e089f7e844fafd12cfddd7eb6f96bef86c0a3 These changes are the result of running the convert-spdx-licenses.py oe-core script. There's no impact to the build, but we will avoid issues when interacting with core QA by the alignment. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2022-02-04T17:21:32+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2022-02-04T17:10:12+00:00 urn:sha1:48c9b9a891709b9761a39553cd8a96e543e0b0b9 oe-core has remove PNBLACKLIST in favour of SKIP_RECIPE, so we update our recipe accordingly to avoid warnings. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-08-02T21:17:53+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2021-07-28T18:22:43+00:00 urn:sha1:d876cfc5bfafa516dee55d04b50b319a22165640 OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-07-07T19:42:17+00:00 hongxu hongxu.jia@windriver.com 2021-07-05T03:24:33+00:00 urn:sha1:6459b6544b9a4d38f145de7c935a5919e758b691 The libmcrypt build issue has been fixed by oe This reverts commit e7a0ea3e0fc43f6c2ec8fee70ec1315014ffbec1. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-04-07T00:34:26+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-04-03T19:51:29+00:00 urn:sha1:32267ea487cb82b19378ee58adbcd105ed4f8648 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-02-07T13:48:39+00:00 Yi Fan Yu yifan.yu@windriver.com 2021-02-05T21:53:10+00:00 urn:sha1:e7a0ea3e0fc43f6c2ec8fee70ec1315014ffbec1 nagios-nsca depends on libmcrypt... However, libmcrypt is considered as abandonware The last release was in 2007. libmcrypt might not be building properly with the upgrade of autoconf to 2.71. Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2019-03-17T00:19:07+00:00 Hongzhi.Song hongzhi.song@windriver.com 2019-03-15T08:55:31+00:00 urn:sha1:b3e9a2b3332382960a9cbf8a6084fbf10a33706c Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>