linux/poky.git/meta/recipes-devtools, branch 3.2_M3

meta: add/fix invalid Upstream-Status tags

2020-09-23T19:54:03+00:00

(From OE-Core rev: 630ce8130598e2bca7231ac28a7cc18b5b942544) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

python3-jinja2: Import from meta-oe/meta-python

2020-09-21T22:54:39+00:00

This is used by some of the results handling code and needed as part of buildtools tarball on various autobuilder worker for testing. ptest is disabled for OE-Core, at least for now since it depends on python3-pytest which in turn has may other dependencies. Acked-by: Tim Orling (From OE-Core rev: 9d30a3b95ef4dce8925f88c8d8d854ed48c5f367) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

python3-markupsafe: Import from meta-oe/meta-python

2020-09-21T22:54:39+00:00

Needed as a dependency of python3-jinja2. ptest is disabled for OE-Core, at least for now since it depends on python3-pytest which in turn has may other dependencies. Acked-by: Tim Orling (From OE-Core rev: 94a04a42826ee95a27abe52d43b31b0f053260d9) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

valgrind: fix memcheck vgtests remove fullpath-after flags

2020-09-17T08:47:46+00:00

Previously in: f75792b28e valgrind: make a few more ptests pass the vagrind test runner was adjusted to suppress part of a path that only exists when run in the yocto ptest environment. Unfortunately this change includes the valgrind version and when valgrind was last updated, the patch was not changed. Rather than continually updating the patch or even generating the version dynamically, we can simply change the expected output for two tests. The reason the option: --fullpath-after=foo was introduced into the effected valgrind ptests was to deal with builds where ccache is used. Compiling with ccache enabled sometimes causes the source file absolute name to be found in a full path that is not the same as $PWD. See commit c80f32e662dfa2a4f046960a25d5b8b7a8821bea in valgrind for more information about changes to the arguments that test badfree3 and varinfo5 run with. There is also a minor fix to add the missing overloading.pm perl package and put the dependencies in alphabetic order. (From OE-Core rev: 9c82b9302c6ee84864e9a9cc870729395804e794) Signed-off-by: Stacy Gaikovaia Signed-off-by: Richard Purdie

bison: remove the parallel build patch

2020-09-17T08:47:46+00:00

Remove the parallel build patch and related fix for parallel build as the issue have already been fixed in bison 3.7.2 (f7b642cf build: fix incorrect dependencies). (From OE-Core rev: 00c7aacf84d094706ed3378a265189d2d6816cfd) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie

qemu: override DEBUG_BUILD

2020-09-17T08:47:45+00:00

Override DEBUG_BUILD for qemu as the qemu upstream states it doesn't work without optimization [1] to fix below build failure when debug build enabled. | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:25: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o: in function `fsdev_co_throttle_request': | /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o:/mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: more undefined references to `unknown_lock_type' follow | collect2: error: ld returned 1 exit status [1]: https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg03873.html (From OE-Core rev: 2d6a15cfb12e72ae3d38f6ecf8c6c2e356e0fda8) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie

Revert "qemu: always define unknown_lock_type"

2020-09-17T08:47:45+00:00

This reverts commit e442924d9ac4e202aec571b5d26bb959b5faaadd. This was rejected upstream and its been pointed out qemu doesn't work without optimization. Instead we should just error if the user attempts to build it without optimization. Signed-off-by: Richard Purdie

go: Update to 1.15.2 minor release

2020-09-14T21:42:30+00:00

This is bug fix release on 1.15 stable version (From OE-Core rev: 0783a84a6b0df84be590f59e70cb80506c774f4d) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

qemu: always define unknown_lock_type

2020-09-14T21:42:30+00:00

When use gcc 10.1.0 and debug build is enabled, there comes below build failure: | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:25: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o: in function `fsdev_co_throttle_request': | /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o:/mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: more undefined references to `unknown_lock_type' follow | collect2: error: ld returned 1 exit status So always define unknown_lock_type to fix the above error. (From OE-Core rev: d88e83d49478a2535575df769329d9b1e6579564) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie

qemu: fix CVE-2020-14364

2020-09-12T13:49:00+00:00

Backport a patch from upstream to fix CVE-2020-14364. (From OE-Core rev: 1ffd4d94e879b338e190a2c4798a4e0bada9b5a7) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie