linux/poky.git/meta/recipes-devtools, branch yocto-4.1.1

quilt: backport a patch to address grep 3.8 failures

2022-11-14T15:59:15+00:00

(From OE-Core rev: a46aad035d800193b740bad2431ce30fae736a23) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni (cherry picked from commit b5001af5c711a373bd2f1ea108c8b597dd40faca) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cmake-native: Fix host tool contamination

2022-11-14T15:59:15+00:00

[v2 hopefully fixes the From: mangling by the ML, no functional changes] Trying to build cmake-native on a host system where curl was built with cmake (resulting in CURLConfig.cmake and friends, which do not use the same naming schemes expected by cmake-native's build process, being installed to a system wide cmake directory like /usr/lib64/cmake/CURL) results in undefined references to all libcurl symbols. The problem is that cmake-native sees and uses the system wide /usr/lib64/cmake/CURL/CURLConfig.cmake, which defines CURL::libcurl and CURL::curl as opposed to setting ${CURL_LIBRARIES} as expected by cmake-native. find_package(CURL) (cmake-native's CMakeLists.txt, line 478) succeeds, but incorrectly uses the system wide CURLConfig.cmake, resulting CMAKE_CURL_LIBRARIES to be set to an empty string (cmake-native's CMakeLists.txt, line 484), causing the cmake-native build to miss -lcurl. The simplest fix is to let cmake know the right value for CURL_LIBRARIES. Making it -lcurl should always work with libcurl-native in recipe-sysroot-native. [YOCTO #14951] (From OE-Core rev: 62b117c382ffd65f6c5d808699b664f70ba6f2d8) Signed-off-by: Bernhard Rosenkränzer Signed-off-by: Alexandre Belloni (cherry picked from commit 2659c735a464c956b4fca0894a5aed27a0fe7e37) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

rust: install rustfmt for riscv32 as well

2022-11-09T17:42:14+00:00

With the above rust arch fixes it builds just fine. (From OE-Core rev: 655b9a0bbe07b33db8aa6ebf7c49f3d9074cc5e0) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit f417ae30c79fac99e2549324ed351f6f63cc4a25) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

qemu-native: Add PACKAGECONFIG option for jack

2022-11-04T23:31:48+00:00

With libjack-devel or jack-audio-connection-kit-devel, qemu-native detects the library/header and tries to build with it. Since its missing from the sysroot, it fails to build. -O2 -fPIE -D_REENTRANT -Wno-undef -MD -MQ libcommon.fa.p/audio_jackaudio.c.o -MF libcommon.fa.p/audio_jackaudio.c.o.d -o libcommon.fa.p/audio_jackaudio.c.o -c ../qemu-6.2.0/audio/jackaudio.c | ../qemu-6.2.0/audio/jackaudio.c:34:10: fatal error: jack/jack.h: No such file or directory | 34 | #include | | ^~~~~~~~~~~~~ | compilation terminated. (From OE-Core rev: 7c8f23aa594175f2169df0d62051bf42d491a1bb) Signed-off-by: Jeremy A. Puhlman Signed-off-by: Alexandre Belloni (cherry picked from commit 27260be388f7f9f324ff405e7d8e254925b4ae90) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

mtools: upgrade 4.0.40 -> 4.0.41

2022-11-04T23:31:48+00:00

disable-hardcoded-configs.patch refreshed for new version Changelo: ========= - Made it possible again to have FAT32 filesystems with less than 0xfff5 clusters - Make FAT32 entries 0 and 1 match what windows 10 does - Misc source code and configure script cleanup (From OE-Core rev: 9ac0de44f11123876a92f7d7819d5ff2c20475b7) Signed-off-by: Wang Mingyu Signed-off-by: Alexandre Belloni (cherry picked from commit b19127f0cd0e10c7180c138284b38c97fa9db7af) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

meson: upgrade 0.63.2 -> 0.63.3

2022-11-04T23:31:48+00:00

(From OE-Core rev: fe33134efbe109b9f3bffa1b05fd6fed8860129c) Signed-off-by: Wang Mingyu Signed-off-by: Alexandre Belloni (cherry picked from commit 3c87597dcde7676858f76c1066cd87195ecc8aef) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

meson: make wrapper options sub-command specific

2022-11-04T23:31:48+00:00

The meson-wrapper adds setup options to facilitate cross-compilation. The current options are exclusive to the setup sub-command and might cause issues with other sub-commands. Update the wrapper to make options sub-command specific. (From OE-Core rev: 4475250ee0d83cc90322f2fcd9ec8df7c05b6903) Signed-off-by: Liam Beguin Signed-off-by: Alexandre Belloni (cherry picked from commit 7bcda141f2019862b4fb5d8dec7956cd8344b420) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

qemu: backport the fix for CVE-2022-3165

2022-11-04T23:31:48+00:00

(From OE-Core rev: d63c5b210b50a2c332a5c309298ec13b510cc7c8) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit d820389728b0f5e085954b4f995da2b2014acedf) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

gcc: Allow -Wno-error=poison-system-directories to take effect

2022-10-25T12:42:03+00:00

The change in commit e903b29f (gcc-cross: pass -Werror=poison-system-directories to compiler stages) made it impossible to disable the error using -Wno-error=poison-system-directories. (From OE-Core rev: 1cb0245539f7d5277fae4e9abc7f2a0130d0caa8) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

opkg-utils: use a git clone, not a dynamic snapshot

2022-10-25T12:42:03+00:00

opkg-utils fetches using a cgit snapshot of a tag, which is not reproducible as the tag could move, not reliable as a future dynamic snapshot could have a different checksum, and a waste of CPU load as these tarballs are built on demand. Switch opkg-utils to use a proper git clone of the relevant SHA. (From OE-Core rev: dafd2631a20ffd94e6f21c46938a010e92b57da4) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie