linux/poky.git/meta/conf, branch uninative-2.8

maintainers.inc: add self for atk, at-spi2-core, at-spi2-atk

2020-02-28T23:11:29+00:00

For GUI automation purposes, strong motivation for accessibility (a11y) via python3-dogtail and python3-pyatspi2, so taking over from Anuj. (From OE-Core rev: fb0a7ab133434febc78ce4f4d00f1192935ad95e) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

go: Update to 1.14 release series

2020-02-28T23:11:29+00:00

(From OE-Core rev: 3daa9684e458b9c926e1a07acd9b1c0fe8bd2e86) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

tune-cortexa72-cortexa53.inc: Adding missing TUNE_FEATURES

2020-02-28T23:11:29+00:00

Without the proper default tune in TUNE_FEATURES, certain variables won't expand correctly. MACHINEOVERRIDES won't add cortexa72-cortexa53: TUNE_CCARGS won't add -mtune=cortexa72.cortexa-53, generating the toolchain incorrectly. Adding missing 'cortexa72-cortexa53' to both TUNE_FEATURES_tune-cortexa72-cortexa53 and TUNE_FEATURES_tune-cortexa72-cortexa53-crypto (From OE-Core rev: eee65bed5ee39051541a0a3f2a311396d6e7326c) Signed-off-by: Jaewon Lee Signed-off-by: Alejandro Enedino Hernandez Samaniego Signed-off-by: Richard Purdie

layer.conf: Consider shared-mime-info and desktop-file-utils siggen safe

2020-02-28T23:11:28+00:00

These are added as dependencies by mime class, which could be inherited along with allarch and dependencies silently go into target specific recipes and which then can result in sstate hash signature mismatches when the allarch recipes are reused for another arch [YOCTO #13805] (From OE-Core rev: 510015ac81df969f690d6c8661b00bebe73b7fca) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

hosttools: add utilities for all supported checksums

2020-02-28T23:11:28+00:00

Only md5sum and sha256sum are currently provided by HOSTTOOLS. Trying to use any other checksum conversion will result in a build failure. Fix it by adding other supported checksum utilities to HOSTTOOLS. (From OE-Core rev: 78155e5fcff9362049b576d20e31c3519c48485b) Signed-off-by: Bartosz Golaszewski Signed-off-by: Richard Purdie

abi_version/sstatesig: Introduce HASHEQUIV_HASH_VERSION

2020-02-28T23:11:28+00:00

We've found we need a way to cause a change in signatures and move to a new hash 'namespace' with hashequiv. This introduces a variable which allows us to do this. (From OE-Core rev: 1c2d5aeae2fa2dfc16bc60b6cf0b310f826337fd) Signed-off-by: Richard Purdie

wayland: add ptest

2020-02-25T10:41:22+00:00

Sadly, meson makes it very difficult to install tests: the test configuration is written into host-specific binary files, which can't be transferred to the target. (unlike autotools where at least everything happens via Makefiles which can be patched and tweaked via sed and env vars) So the configuration has to be entirely recreated in shell. I managed this for wayland, but weston proved too difficult. I had filed bugs asking upstream to make the tests installable: https://gitlab.freedesktop.org/wayland/wayland/issues/146 https://gitlab.freedesktop.org/wayland/weston/issues/368 (From OE-Core rev: 296ee10bb8491278f050fb9d55f42b0bcf663382) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

libidn: Move to meta-oe

2020-02-25T10:41:22+00:00

There are no users left in OE-core. (From OE-Core rev: 2c5d140a8a2b794b36ed9535afc278cec2ef306f) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie

mdadm: drop from PTESTS_SLOW

2020-02-23T23:33:48+00:00

There are two primary reasons for this: 1. mdadm test suite tends to work like this do_action sleep arbitrary_amount check_result This is unreliable, and arbitrary_amount may or may not be enough. I have confirmed this by increasing the amount, and seeing more tests pass than before. 2. The test suite aborts half way through because one of the mdadm binaries segfaults. This indicates that upstream isn't actually running the suite anymore, and in this situation we shouldn't be relying on it either. (From OE-Core rev: e21021dc00ec76c76cc361e15bc83a89083c9e72) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

binutils: Upgrade to 2.34 release

2020-02-22T23:57:27+00:00

Details of changelog [1] Removing bfd/ld patch to enable PE targets, instead use specific emulations via --enable-targets for x86_64 Re-arrange/forward-port patches and upgrade libctf configure to libtool 2.4 patch rpaths are no longer emitted into elfedit/readelf therefore no need of chrpath anymore Instead of pre-generating configure scripts and house them in libtool patch, generate them during configure. This also ensures that we do not patch configure directly but rather the sources which generate it Package newly added libctf library [1] https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html (From OE-Core rev: 82f7d5cfc2ab02f39b69c0f8697d660936422d4a) Signed-off-by: Khem Raj Cc: Christopher Clark Signed-off-by: Richard Purdie