summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
AgeCommit message (Collapse)Author
2022-01-04meson: Handle qemu riscv issuesRichard Purdie
In qemu, they merged the 32 and 64 bit riscv variants into one target for meson purposes but this isn't officially supported by upstream meson. In normal builds this would just be a warning but in OE, this is fatal. Avoid the fatal errors for now and build as qemu intended whilst this is resolved by the upstreams. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04rpm: remove tmp folder created during installSamuli Piippo
nativesdk-rpm build is also affected by the stray /var/tmp created during the rpm install. Remove it to fix QA Issue: nativesdk-rpm installs files in /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/var/volatile, but it is expected to be empty [empty-dirs] Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04rpm: fix CVE-2021-3521Changqing Li
Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04valgrind: make run-ptest betterRandy MacLeod
There were warnings about non-existent files when there was a duplicate in the remove-for-aarch list and the non-deterministic lists so check if the files still exists before trying to deal with it. Also restore the tests in the opposite order that they were hidden. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04valgrind: skip boost_thread for aarch64 ptestsRandy MacLeod
The drd/tests/boost_thread test passes when run interactively on qemuarm64 but fails for most runs when run in qemu on an arm worker such as ubuntu1804-arm-1 from the Yocto autobuilder cluster. Skip the test until we fix the problem. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04valgrind: remove duplicate and skipped tests from remove-for-aarch64Randy MacLeod
The valgrind ptest script warns about tests such as: mv: cannot stat 'drd/tests/bar_bad_xml.vgtest': No such file or directory Since these tests were either in both remove-for-* lists or were not installed since they fail everywhere as noted in: 85a0d61025 valgrind: fix the remaining ptest failures 984ffe3ab4 valgrind: Disable leak_cpp_interior test remove them from the remove-for-aarch64 list Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04valgrind: backport rseq work-aroundRandy MacLeod
Using glibc-2.35-alpha, valgrind ptests mostly all fail with the error: WARNING: unhandled amd64-linux syscall: 334 You may be able to write your own handler. With this patch applied qemux86-64 ptest results were: TOTAL: 728 PASSED: 709 FAILED: 0 SKIPPED: 19 This patch implements the Linux rseq syscall as ENOSYS while a proper fix is being worked on as desribed in the patch commit log. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-04valgrind: Add util-linux-taskset ptest dependencyRandy MacLeod
We are using taskset to improve the reproducability of tests listed in: meta/recipes-devtools/valgrind/valgrind/taskset_nondeterministic_tests so we need to have the ptests depend on util-linux-taskset. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-22binutils: CVE-2021-42574pgowda
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b3aa80b45c4f46029efeb204bb9f2d2c4278a0e5] [RP: Merge uint -> unsigned int change] Signed-off-by: pgowda <pgowda.cve@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-22qemu: Add selinux PACKAGECONFIGRichard Purdie
We're seeing failures on systems with old selinux headers. Add a PACKAGECONFIG entry so that we don't try and build this unless enabled. I'll leave dependencies to someone who wants it and can test, I just need to fix build failures right now as this shouldn't be enabled. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-21gcc: Update status of musl stddef.h patchKhem Raj
This patch has been accepted upstream Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-21python3: backport a fix so the test suite passes with OpenSSL 3.0.1Ross Burton
The test suite makes incorrect assumptions about OpenSSL versions post- 3.0, so backport the fix for the test suite. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-21python3-importlib-metadata: upgrade 4.8.2 -> 4.9.0wangmy
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-20qemu: Upgrade 6.1.0 -> 6.2.0Richard Purdie
Add config option for pulseaudio Change audio to default mode since quoting of list of devices is broken in meson Drop patch where code changed completed upstream Refresh other patches Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-20qemu: add patch to set minimum kernel version for riscv32Matt Madison
which enables us to drop the -r option on qemu-static-riscv32 invocations. Signed-off-by: Matt Madison <matt@madison.systems> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-20python3-pyelftools: Depend on debugger, pprintChaitanya Vadrevu
python3-pyelftools uses python3-debugger, python3-pprint. So add dependencies on these packages. Signed-off-by: Chaitanya Vadrevu <chaitanya.vadrevu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17python3-idna: Update license to Unicode-TOURichard Purdie
The correct SPDX license for the test data contained in this code appears to be Unicode-TOU. Update the LICENSE field to match and avoid package QA warnings. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17repo: update 2.18 -> 2.19Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17go: upgrade 1.17.4 -> 1.17.5Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17dpkg: update 1.20.9 -> 1.21.1Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17python3-setuptools: upgrade 59.4.0 -> 59.5.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17elfutils: update patch submitted upstreamAlexander Kanavin
As that's what upstream prefers. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17python3-hypothesis: upgrade 6.30.0 -> 6.31.4Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17btrfs-tools: upgrade 5.15 -> 5.15.1Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-17gcc: Fix CVE-2021-42574pgowda
Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bd5e882cf6e0def3dd1bc106075d59a303fe0d1e] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=51c500269bf53749b107807d84271385fad35628] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=1a7f2c0774129750fdf73e9f1b78f0ce983c9ab3] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bef32d4a28595e933f24fef378cf052a30b674a7] Signed-off-by: pgowda <pgowda.cve@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-14bootchart2: remove wait_boot logicMingli Yu
When boot with "init=/sbin/bootchartd" as below: # runqemu qemux86 bootparams="init=/sbin/bootchartd" There are two bootchartd process after boot [1]. # ps -ef | grep bootchart root 101 1 0 03:27 ? 00:00:00 /bin/sh /sbin/bootchartd root 103 101 8 03:27 ? 00:00:02 /lib64/bootchart/bootchart-collector 50 root 106 1 0 03:27 ? 00:00:00 /bin/sh /sbin/bootchartd root 792 106 0 03:27 ? 00:00:00 /lib64/bootchart/bootchart-collector --usleep 1000000 root 794 725 0 03:27 ttyS0 00:00:00 grep bootchart # /sbin/bootchartd stop [bootchart] bootchart-collector started as pid 596 with 2 args: [bootchart] '--dump' [bootchart] '/tmp/bootchart.3lXpVDAq3v' [bootchart] Extracting profile data from pid 204 [bootchart] map 0xbed9a000 -> 0xbedbb000 size: 132k from 'bed9a000' 'bedbb000' [bootchart] read 135168 bytes of 135168 [bootchart] reading 150 chunks (of 150) ... [bootchart] wrote 18760 kbB [bootchart] bootchart-collector pid: 596 unmounted proc / clean exit But there still one process exist after the above stop command finish. # ps -ef | grep bootchartd root 202 1 0 09:09 ? 00:00:00 /bin/sh /sbin/bootchartd root 629 516 0 09:10 ? 00:00:00 grep bootchartd Remove the wait_boot which used to wait the boot process to finish to make sure only one bootchartd process and meanwhile we don't need the wait_boot logic because we either use "/sbin/bootchartd stop" to stop the bootchartd manually or install package bootchartd-stop-initscript altogether with bootchart2 to stop bootchartd automatically after boot. After patch: # ps -ef | grep bootchart root 101 1 0 03:36 ? 00:00:00 /bin/sh /sbin/bootchartd root 103 101 6 03:36 ? 00:00:04 /lib64/bootchart/bootchart-collector 50 root 596 592 0 03:37 ttyS0 00:00:00 grep bootchart [1] https://github.com/xrmx/bootchart/issues/94 Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-14python3-cython: upgrade 0.29.24 -> 0.29.25wangmy
Changelog: ================ Bugs fixed ---------- * Several incompatibilities with CPython 3.11 were resolved. (Github issues #4411, #4414, #4415, #4416, #4420, #4428, #4473, #4479, #4480) * Some C compiler warnings were resolved. (Github issue #4439) * C++ "std::move()" should only be used automatically in MSVC versions that support it. (Github issue #4191) * The "Py_hash_t" type failed to accept arbitrary "index" values. (Github issue #2752) * Avoid copying unaligned 16-bit values since some platforms require them to be aligned. Use memcpy() instead to let the C compiler decide how to do it. (Github issue #4343) * Cython crashed on invalid truthiness tests on C++ types without "operator bool". (Github issue #4348) * The declaration of "PyUnicode_CompareWithASCIIString()" in "cpython.unicode" was incorrect. (Github issue #4344) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12patchelf: upgrade 0.14.2 -> 0.14.3Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12subversion: remove obsolete support for renamed libtoolRoss Burton
libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12qemu: remove obsolete support for renamed libtoolRoss Burton
libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12pkgconfig: remove obsolete support for renamed libtoolRoss Burton
libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12binutils: don't expect libtool to be host-prefixedRoss Burton
We update the libtool m4 files in binutils with the latest files from our patched libtool so that we can use the --with-libtool-sysroot option. Remove the chunks that are specific to the libtool renaming, which now doesn't happen. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12libtool: don't prefix the installed binaryRoss Burton
Typically libtool installs the binary to 'libtool' in the source tree, but we've got patches to rename this to ${host_sys}-libtool. As this isn't standard any upstream that don't respect the LIBTOOL variable need to be told explicitly where libtool is, which is a long-term maintenance burden for us on top of the initial libtool patches. The reasoning for this renaming appears to stem from the design to be sure that we're using our new/patched libtool and not the host's binary. However, now that we have HOSTTOOLS, there's no way to run the host libtool so this argument is moot. This patch removes the libtool renaming, follow-up patches remove the required modifications from the rest of the recipes. [RP: Remove commented patch lines] Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12elf: Discard input .note.gnu.build-id sectionsValerii Chernous
Originally issue: building of glibc 2.32 or 2.34 with option "-Wl,--build-id" produce libc.so.6 with section ".note.gnu.build-id" that have invalid(double, 0x48) section size. It happens because glibc use sublibraries for linking libc.so.6 ld produce this sublibraries with build-id section and on last linking stage loads this sections as input for linking. ld should create new(valid) ".note.gnu.build-id" into function ldelf_setup_build_id on last linking stage but it skip creating because build-id section already exists. As result libc.so.6 contain ".note.gnu.build-id" with build-ids from sublibraries and without valid build-id Howto solved: 1. Discard input .note.gnu.build-id sections. 2. Clear the build ID field before writing. 3. Use bfd_make_section_anyway_with_flags to create the output .note.gnu.build-id section. Upstream-Status: Backport Reference to upstream patch: [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1f1d0f8888a6c944e612b416a2a6e11abcf5199f] Signed-off-by: Valerii Chernous <vchernou@cisco.com> Signed-off-by: Valery Chernous <valery.chernous@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12python3: udpate to 3.10.1Oleksandr Kravchuk
Refreshed patches. Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12meson: upgrade 0.60.1 -> 0.60.2Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12cmake: upgrade 3.22.0 -> 3.22.1Changqing Li
This upgrade include a bug fix: Refer: https://gitlab.kitware.com/cmake/cmake/-/issues/22963 https://gitlab.kitware.com/cmake/cmake/-/commit/643fc46bdc13dd57584d5d77eee30a99308ba896 Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12binutils: Drop mips XLP support patchRichard Purdie
The kernel has dropped this as of 5.16 and we don't want to carry such patches without active maintainers for such targets. It isn't clear who would even have such hardware and it isn't something we can support. It would be best maintained as a separate layer by those who can test it if needed. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12binutils: Drop mips default target patchRichard Purdie
Similarly to the recent gcc change, we make gcc default to the 64 bit target through configuration now so we don't need to patch this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12binutils: Add more detail to the ppc patchRichard Purdie
This adds useful detail from the orginal commit. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-12binutils: Drop mips gold patchRichard Purdie
As mentioned in a followup to the patch upstream: https://sourceware.org/legacy-ml/binutils/2016-08/msg00215.html "With 2.16.1, --enable-gold is just ignored when building on mips" so we don't need the patch since 2.16.1. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09python3-setuptools: upgrade 59.2.0 -> 59.4.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09python3-ruamel-yaml: upgrade 0.17.16 -> 0.17.17Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09python3-pbr: upgrade 5.7.0 -> 5.8.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09python3-more-itertools: upgrade 8.11.0 -> 8.12.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09python3-markdown: upgrade 3.3.4 -> 3.3.6Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09python3-hypothesis: upgrade 6.24.3 -> 6.30.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09mmc-utils: upgrade to latest revisionAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09ccache: upgrade 4.5 -> 4.5.1Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-12-09gcc: Add CVE-2021-37322 to the list of CVEs to ignoreRichard Purdie
The CVE applies to binutils 2.26 and not to gcc so ignore there. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>