summaryrefslogtreecommitdiffstats
path: root/meta
AgeCommit message (Collapse)Author
4 daysRevert "systemd hack"rpurdie/t222Richard Purdie
This reverts commit 0ce79d9d867af8b36a10edfcb98401fcbcc5f96c.
4 dayssystemd hackRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysselftest: Add tests for populate_sdk taskPavel Zhukov
Two tests to cover both installing package with IMAGE_INSTALL as well as installing versioned dependencies of the package (using perl (>= 5.XX). Related: [Yocto #13338] [Yocto #14995] [Yocto #14066] Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysdummy-sdk-package.inc: Specify providers versionPavel Zhukov
Some of the packages require versioned providers (DEPENDS: perl (>= 5.38) is an example and for such packages do_populate_sdk fails because dummy packages provided unversioned packages (PROVIDES: perl) which doesn't meet the version requirement. Specify 999.9-r9 version for such provides to work this around Fixes [Yocto #14995] Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayspackage_deb: Revert versioned providers workaroundPavel Zhukov
dpkg and apt seem to handle versioned provides correctly now [1] so this workaround is not needed anymore. This fixes [Yocto #14995] for package_deb. [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#virtual-packages-provides Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysdummy-sdk-package.inc: Filter packages which are marked for installationPavel Zhukov
if packages is provided by dummysdk and in the same time marked for installation with IMAGE_INSTALL it causes conflict in apt because virtual providers are not taken into account if package is asked to be installed explicitly. Filter such packages from provides/conflicts to workaround this problem. This workaround brakes RPM usecase because of file conlicts with DUMMYPROVIDES, use DUMMYPROVIDES_PACKAGES_MULTILIB instead (which doesn't include file based conflicts). While this is needed for the case of package_deb only adding it for all package managers to not complicate the code. Fixes: [Yocto #13338] [Yocto #14066] Fixes: The following information may help to resolve the situation: The following packages have unmet dependencies: target-sdk-provides-dummy : Conflicts: bash E: Unable to correct problems, you have held broken packages. Signed-off-by: Pavel Zhukov <pavel@zhukoff.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysRevert "wip"Richard Purdie
This reverts commit a25654ee14cc4dd0685ccc722b61bbfd7559b273.
4 dayswipRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayslicense/license_image: Fix license file layout to avoid overlapping filesRichard Purdie
Currently DEPLOY_DIR/licenses is added to SSTATE_ALLOW_OVERLAP_FILES. This leads to bugs since when one MACHINE_ARCH recipes is cleaned, it removes the files for another which then results in later build failures as license files disappear. The solution is to include SSTAGE_PKGARCH in the path names to the license files. That does mean a search has to be used to find the correct license files for a given PN but that can be done via SSTATE_ARCHS. The implication for other tools is the layout has changed so tools will need to adapt to the new paths. The benefit is no more strange build failures such as from patterns like: MACHINE=qemux86-64 bitbake core-image-minimal MACHINE=genericx86-64 bitbake core-image-minimal MACHINE=qemux86-64 bitbake linux-yocto -c clean MACHINE=genericx86-64 bitbake core-image-minimal -C rootfs [YOCTO #14123] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayspseudo: Quiet loggingRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysshadow experimentRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysRevert "oeqa/selftest: change deprecated usage of run_serial"Richard Purdie
This reverts commit cd265a1a1f00fdf3274f5a910bb0b86d05d1b378.
4 daysRevert "fixup"Richard Purdie
This reverts commit e2e378a8a0fd295823947361d8db1c0e9cc69976.
4 daysoeqa/selftest: change deprecated usage of run_serialLouis Rannou
Prefer the new function run_serial_socket. Change calls where the modification is easy. (From OE-Core rev: 0f1fc49f44db5e867ae831c74602ed2d55184942) Signed-off-by: Louis Rannou <lrannou@baylibre.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayskernel.bbclass: hoist up "unset S" bbfatal from kernel-yocto.bbclass to ↵Luca Ceresoli
kernel.bbclass Writing a simple recipe that inherits kernel.bbclass and downloads a kernel tarball (e.g. a mainline release from kernel.org) via http or ftp fails with either: ERROR: linux-acme-6.3.3-r0 do_configure: oe_runmake failed ... | make: *** No rule to make target 'oldnoconfig'. Stop. or (seen on a different setup, based on kirkstone): ... do_populate_lic: QA Issue: ... LIC_FILES_CHKSUM points to an invalid file: .../work-shared/.../kernel-source/COPYING [license-checksum] This happens when not setting S in the recipe. In this case, kernel.bbclass sets it to ${STAGING_KERNEL_DIR} (${TMPDIR}/work-shared/${MACHINE}/kernel-source). This means that in do_symlink_kernsrc(), the 'if s != kernsrc' never triggers and thus the kernel tree will not me moved into work/shared, which results in an empty work-shared/.../kernel-source directory. When downloading a tarball it is usually not required to set S in recipes, so this is not obvious here and the error message does not point to the problem or its solution. There is such a check in kernel-yocto.bbclass though, so move it to kernel.bbclass so that also kernel recipes not based on kernel-yocto can benefit from it. The check is moved: - from the beginning of do_kernel_checkout() in kernel-yocto - to the end of do_symlink_kernsrc() in kernel.bbclass and since do_kernel_checkout is executed 'after do_symlink_kernsrc', the code flow does not change in a relevant way when using linux-yocto. (From OE-Core rev: 8b5a8924204287737f47c660efe9ea7a89313d57) Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayscore-image-minimal: increase extra space to pass df.py oeqa runtime testMikko Rapeli
testimage.bbclass requires that ssh communication with target works and then it runs oeqa runtime tests with that. Tests like df.py check that there is more than 5Mb free space on the rootfs on target. Sadly latest core-image-minimal only has 1.5 Mb free space if ssh-server-dropbear is added to it. Thus by default, core-image-minimal is now failing oeqa rutime df.py test. Fix this by increasing core-image-minimal rootfs size by 5Mb if testimage.bbclass is used which implies adding either ssh-server-dropbear or ssh-server-openssh to the target rootfs. (From OE-Core rev: 0210c1314a066c807dd5876c091cdc8dd04d2fda) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysppp-dialin: Fix groupname gid change warningJD Schroeder
This patch fixes warnings when useradd-staticids.bbclass is used and USERADD_PARAM is used to add the user to a group that has not been explicitly created yet. By adding the GROUPADD_PARAM for the new group being used the warnings for changing the gid from GID-OLD to GID-NEW is eliminated. Warning fixed: ppp-dialin: Changing groupname nogroup's gid from (WXYZ) to (JKLM), verify configuration files! (From OE-Core rev: e0713aace14b1a2600ea1ad4c72e5e0aa962b639) Signed-off-by: JD Schroeder <sweng5080@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysoeqa/qemurunner: Extra debugRichard Purdie
(From OE-Core rev: 312a6a4f0a586f5e4c85bd59c34667e4928b6869) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysrust-cross-canadian: Fix file conflicts for arm and aarch64Deepthi Hemraj
[YOCTO #15061] Rust multilib sdks broken because of the conflicts between attempted installs of rust-cross-canadian for arm and aarch64. Arm and aarch64 target architectures are trying to install cargo.sh and rust.sh in the same path which resulted in the issue. The current patch modifies CARGO_ENV_SETUP_SH and RUST_ENV_SETUP_SH macros based on the architecture. Hence, creates different file names for the environment setup scripts and resolves the issue. (From OE-Core rev: 97f0272681be5c20182d2e2115d4dfa7da456168) Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysmake-mod-scripts: exclude rm_workJose Quaresma
- Add the recipe to the RM_WORK_EXCLUDE With rm_work active, external module signing throws an error: scripts/sign-file: error while loading shared libraries: libcrypto.so.3: can not open shared object file: No such file or directory Preserve libraries that sign-file script needs during runtime. Some solutions [1][2] for this problem have already been submitted on the mailing list but none of them get merged: [1] Fix using RM_WORK_EXCLUDE_ITEMS https://lists.openembedded.org/g/openembedded-core/message/180113 [2] Fix using static linking https://lists.openembedded.org/g/openembedded-core/message/182024 (From OE-Core rev: 2a3decb71286773814b26fa56deba2321939ff04) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysusbutils: upgrade 015 -> 017Alexander Kanavin
Drop CFLAGS (containing host paths) from installed pkg-config file. (From OE-Core rev: 6ef8aca5587161ac63cbf6a04386792f0121884f) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysRevert "sstatesig: Ensure spdx dependencies update when abisafe recipes change"Richard Purdie
This reverts commit fd9261726b19bbdd6e7709f7d1ae2dc4a2dfa59b. (From OE-Core rev: c8cb0636909de594ce460c47940e91a0ebea8c48) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayssstatesig: Ensure spdx dependencies update when abisafe recipes changeRichard Purdie
If you build openssh, bump the version of base-passwd, then rerun openssh:do_create_spdx, it will fail due to references to the old version of base-passwd. This is due to base-passwd being listed in SIGGEN_EXCLUDERECIPES_ABISAFE. Ignore these recipes for the purposes of create_spdx and force rebuilds when things change. (From OE-Core rev: 5d7098077b177208a064b3edfbe680ca78408fbb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysno-gplv3: Add workarounds for update-alternatives and ptestRichard Purdie
Document the tribal knowledge that we have to disable ptests for gplv3. Also document the workaround for update-alternatives issues with bash and opkg-utils. As with anything in this file, the exclusions come at a cost. (From OE-Core rev: 9553861ba13effe72d0dbec71b11e416115b2556) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysimage.bbclass/rootfs: set and unpack package-databaseJohannes Schneider
set the package-database of a "lower image" to unpack and build upon when installing packages for the current image. This way a lean image will be created, which only holds the packages that are not already present in the lower image, that then could be used with overlayfs or systemd-sysext to extend the "lower image" on demand; for development purposes on an RO lower image for example. (From OE-Core rev: a867c4363562ac328618e2ea0070ee6cf5af0ec2) Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysclasses: add a systemd-sysext image classJohannes Schneider
systemd-sysext can load a raw-image containing usr/ and opt/ folders to mount them as RO overlay over the rootfs, to "extend" the systems. This class provides the necessary changes/additions to the enclosed file-system so that systemd-sysext accepts the extension for "merge" into the rootfs. With such an created image, placed into the correct folder (see [1]), `systemd-sysext list` should be able to list the "extension" and `systemd-sysext merge` should enable the overlay. On both commands a preceding "SYSTEMD_LOG_LEVEL=debug" can aide in figuring out what is amiss. The strict name checking systemd-sysext does against the name of extension-release.NAME file, is disabled, as there is only one such in the resulting image. This is done to allow a user to freely rename the resulting image file. Note that for e.g. squashfs, the kernel needs CONFIG_SQUASHFS_XATTR=y Link: https://www.freedesktop.org/software/systemd/man/latest/systemd-sysext.html Link: https://0pointer.net/blog/testing-my-system-code-in-usr-without-modifying-usr.html (From OE-Core rev: 516497879379d20ec8db85c158dc557d05b92958) Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysimage.bbclass/rootfs: archive and deploy opkg package databaseJohannes Schneider
archive the package database after the rootfs has been put together as *rootfs-pkdbfs.tar.gz, and put it into the deploy folder. This creates a snapshot of the package mangers state at the point in time when all dependencies have been resolved and installed; which can be used by "follow up" images to be built upon. (From OE-Core rev: d0fae3ad20a33e468d480ea393cbd341f7a7073b) Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysglibc: fix multilib headers conflict for armKai Kang
The header files conflic when multilib enabled for arm: | Error: Transaction test error: | file /usr/include/finclude/math-vector-fortran.h conflicts between attempted installs of lib32-libc6-dev-2.39+git0+312e159626-r0.armv7at2hf_neon and libc6-dev-2.39+git0+312e159626-r0.cortexa72 Invoke function oe_multilib_header to resolve it. (From OE-Core rev: c936698c64515b9de6ff99fdd3894ec8f1ef8478) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysimage-tests: Add initial image test png filesEilís 'pidge' Ní Fhlannagáin
This is an initial commit of png's we can use to test qemu image testing against. (From OE-Core rev: a186c9cf9ca07fdb05054be9a791529248865b1c) Signed-off-by: Eilís 'pidge' Ní Fhlannagáin <pidge@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysRevert "libbsd: Fix conflict error when enable multlib."Richard Purdie
This reverts commit 1ca03c78ea588fd54675cffd5d55ce6cfad02870. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysRevert "shadow: update 4.14.2 -> 4.15.0"Richard Purdie
This reverts commit e919ef9f9c01a56afe6065eb96810f31d7c43cca. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayslibbsd: Fix conflict error when enable multlib.Lei Maohui
Error: Transaction test error: file /usr/include/bsd/sys/cdefs.h conflicts between attempted installs of libbsd-dev-0.12.1-r0.core2_64 and lib32-libbsd-dev-0.12.1-r0.core2_32 The difference of bsd/sys/cdefs.h between libbsd-dev and lib32-libbsd-dev is as following: /* Define the ABI for the current system. */ -#define LIBBSD_SYS_TIME_BITS 64 +#define LIBBSD_SYS_TIME_BITS 32 #define LIBBSD_SYS_HAS_TIME64 1 (From OE-Core rev: 1ca03c78ea588fd54675cffd5d55ce6cfad02870) Signed-off-by: Lei Maohui <leimaohui@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayscve-check: Add provision to exclude classesDhairya Nagodra
- There are times when exluding a package that inherits a particular class/classes may be desired. - This provides the framework for that via the variable: CVE_CHECK_CLASS_EXCLUDELIST (From OE-Core rev: f62b74f9a837b74a9e2292a35cae21359431a825) Signed-off-by: Dhairya Nagodra <dnagodra@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayssystemd-conf: Convert to use a dedicated UNPACKDIRRichard Purdie
Avoid: WARNING: systemd-conf-1_1.0-r0 do_unpack: systemd-conf: the directory ${WORKDIR}/${BP} (tmp/work/genericarm64-poky-linux/systemd-conf/1.0/systemd-conf-1.0) pointed to by the S variable doesn't exist - please set S within the recipe to point to where the source has been unpacked to by using a dedicated unpack directory for sources. (From OE-Core rev: 7272eab1e3b7d1002f5761db0d40377abac660f8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayspython3-pycparser: cleanup RDEPENDSGuðni Már Gilbert
- Drop python3-pprint, the source code no longer imports this module - Drop python3-ply, ply package is bunled into pycparser, making the external python3-ply dependency not useful. This seems to have been changed a long time ago in version 2.09 (2012.12.27) Note about python3-netclient: It can be removed at a later date. There is one 'unused' import for base64 in the ply source. Once that is cleaned up, python3-netclient can be removed. (From OE-Core rev: e2b71add04e9b55dbc762a91dc232fc2959f14e8) Signed-off-by: Guðni Már Gilbert <gudnimar@noxmedical.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysvalgrind: Upgrade to 3.23.0Khem Raj
Drop backports already available in this release This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android, X86/Solaris, AMD64/Solaris, AMD64/MacOSX 10.12, X86/FreeBSD, AMD64/FreeBSD and ARM64/FreeBSD There is also preliminary support for X86/macOS 10.13, AMD64/macOS 10.13 and nanoMIPS/Linux. * ==================== CORE CHANGES =================== * --track-fds=yes will now also warn about double closing of file descriptors. Printing the context where the file descriptor was originally opened and where it was previously closed. * --track-fds=yes also produces "real" errors now which can be suppressed and work with --error-exitcode. When combined with --xml the xml-output now also includes FdBadClose and FdNotClosed error kinds (see docs/internals/xml-output-protocol5.txt). * The option --show-error-list=no|yes now accepts a new value all. This indicates to also print the suppressed errors. This is useful to analyse which errors are suppressed by which suppression entries. The valgrind monitor command 'v.info all_errors' similarly now accepts a new optional argument 'also_suppressed' to show all errors including the suppressed errors. * ================== PLATFORM CHANGES ================= * Added ARM64 support for FreeBSD. * ARM64 now supports dotprod instructions (sdot/udot). * AMD64 better supports code build with -march=x86-64-v3. fused-multiple-add instructions (fma) are now emulated more accurately. And memcheck now handles __builtin_strcmp using 128/256 bit vectors with sse4.1, avx/avx2. * S390X added support for NNPA (neural network processing assist) facility vector instructions VCNF, VCLFNH, VCFN, VCLFNL, VCRNF and NNPA (z16/arch14). * X86 recognizes new binutils-2.42 nop patterns. * ==================== TOOL CHANGES =================== * The none tool now also supports xml output. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. 283429 ARM leak checking needs CLEAR_CALLER_SAVED_REGS 281059 Cannot connect to Oracle using valgrind 328563 make track-fds support xml output 362680 --error-exitcode not honored when file descriptor leaks are found 369723 __builtin_longjmp not supported in clang/llvm on Android arm64 target 390269 unhandled amd64-darwin syscall: unix:464 (openat_nocancel) 401284 False positive "Source and destination overlap in strncat" 428364 Signals inside io_uring_enter not handled 437790 valgrind reports "Conditional jump or move depends on uninitialised value" in memchr of macOS 10.12-10.15 460616 disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP) 463458 memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 463463 none/tests/amd64/fma fails when executed on a x86-64-v3 system 466762 Add redirs for C23 free_sized() and free_aligned_sized() 466884 Missing writev uninit padding suppression for _XSend 471036 disInstr_AMD64: disInstr miscalculated next %rip on RORX imm8, m32/64, r32/6 471222 support tracking of file descriptors being double closed 474160 If errors-for-leak-kinds is specified, exit-on-first-error should only exit on one of the listed errors. 475498 Add reallocarray wrapper 476025 Vbit expected test results for Iop_CmpGT64Ux2 are wrong 476320 Build failure with GCC 476331 clean up generated/distributed filter scripts 476535 Difference in allocation size for massif/tests/overloaded-new between clang++/libc++ and g++/libstdc++ 476548 valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold 476708 valgrind-monitor.py regular expressions should use raw strings 476780 Extend strlcat and strlcpy wrappers to GNU libc 476787 Build of Valgrind 3.21.0 fails when SOLARIS_PT_SUNDWTRACE_THRP is defined 476887 WARNING: unhandled amd64-freebsd syscall: 578 477198 Add fchmodat2 syscall on linux 477628 Add mremap support for Solaris 477630 Include ucontext.h rather than sys/ucontext.h in Solaris sources 477719 vgdb incorrectly replies to qRcmd packet 478211 Redundant code for vgdb.c and Valgrind core tools 478624 Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 478837 valgrind fails to read debug info for rust binaries 479041 Executables without RW sections do not trigger debuginfo reading 480052 WARNING: unhandled amd64-freebsd syscall: 580 480126 Build failure on Raspberry Pi 5 / OS 6.1.0-rpi7-rpi-v8 480405 valgrind 3.22.0 "m_debuginfo/image.c:586 (set_CEnt): Assertion '!sr_isError(sr)' failed." 480488 Add support for FreeBSD 13.3 480706 Unhandled syscall 325 (mlock2) 481127 amd64: Implement VFMADD213 for Iop_MAddF32 481131 [PATCH] x86 regtest: fix clobber lists in generated asm statements 481676 Build failure on Raspberry Pi 5 Ubuntu 23.10 with clang 481874 Add arm64 support for FreeBSD 483786 Incorrect parameter indexing in FreeBSD clock_nanosleep syscall wrapper 484002 Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm() 484426 aarch64: 0.5 gets rounded to 0 484480 False positives when using sem_trywait 484935 [patch] Valgrind reports false "Conditional jump or move depends on uninitialised value" errors for aarch64 signal handlers 485148 vfmadd213ss instruction is instrumented incorrectly (the remaining part of the register is cleared instead of kept unmodified) 485487 glibc built with -march=x86-64-v3 does not work due to ld.so strcmp 485778 Crash with --track-fds=all and --gen-suppressions=all n-i-bz Add redirect for memccpy To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed above. (From OE-Core rev: 1c931a1459ab5787e84147b8a591f4616140a4e8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayscpio: mark CVE-2023-7216 as disputedRoss Burton
Upstream consider the behaviour described in this CVE as intentional, and provide an option to stop it. (From OE-Core rev: 96863a72607e0a9a5d9ea538cebbd717d93cd9d6) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysRevert "insane: Add warning for WORKDIR instead of UNPACKDIR"Richard Purdie
This reverts commit 9d804d07b96b103397583228e8066407785167c1. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysinsane: Add warning for WORKDIR instead of UNPACKDIRRichard Purdie
(From OE-Core rev: a17fc13e7683b0837738d5fe1b5148fa1a771c47) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysinsane: Warn about S == WORKDIRRichard Purdie
Where a recipe uses WORKDIR as S, add a warning since we're going to stop supporting this soon. (From OE-Core rev: fab188470330b99fac2c75d682e7b66ceb8e4479) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysbase: Switch UNPACKDIR to a subdir of WORKDIRRichard Purdie
Change do_unpack to unpack files to a subdirectory of WORKDIR instead of WORKDIR itself. There are several good reasons for this but it is mainly about being able to isolate the output of the unpack task and tell the files apart from other things which are created in workdir (logs, sysroots, temp dirs and more). This means that when the do_unpack task reruns, we can clean UNPACKDIR and know we have a standard point to start builds from. It also makes code in tools like devtool and recipetool easier. To reduce the impact to users, if a subdirectory under UNPACKDIR matches the first subdirectory under WORKDIR of S, that directory is moved into position inside WORKDIR. This preserves the behaviour of S = "${WORKDIR}/git", S = "${WORKDIR}/${BPN}" and other commonly used source directory setups. The directory is moved since sadly many autotools based projects can't cope with symlinks in their paths. (From OE-Core rev: 9f83430297285fdec0684c7ffd3db1ff5265a164) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysdevtool: Drop oe-local-files and simplifyRichard Purdie
The only real reason for oe-local-files was to support S = WORKDIR. With changes to drop support for that, it makes sense to simplify devtool and to try and make both the code and the processes/workflows simpler. This patch drops support for S = WORKDIR, removes oe-local-files and then updates the test cases to match this new situation. At the code level, we assume we can always now track code changes using git and that things committed into git are handled as patches (as before) but delta against HEAD is saved as specific file level changes to the recipe. One test is disabled as it is no longer approproate. It is being keped until we can make WORKDIR != UNPACKDIR at which point it should be revisited. (From OE-Core rev: 6b782aece619377d422e1eeb38276709fc1b8009) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysat: Tweak UNPACKDIR referenceRichard Purdie
${UNPACKDIR}/${BP} is ${S} so use the correct variable. (From OE-Core rev: 8b13c5d92c7d4b90743ae5c92f6f40170d927c53) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysrecipes: Switch away from S = WORKDIRRichard Purdie
Where recipes use S = ${WORKDIR}, change them to set UNPACKDIR to a subdir of WORKDIR and make S point at this instead. I've chosen not to force S into any standard UNPACKDIR we may pick in future just so the S = UNPACKDIR case is clearly visible by the directory naming under WORKDIR as that should aid usability. (From OE-Core rev: 780b4ed4e536381a0b502e61c813e61e77c6436e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysrecipes: Start WORKDIR -> UNPACKDIR transitionRichard Purdie
Replace references of WORKDIR with UNPACKDIR where it makes sense to do so in preparation for changing the default value of UNPACKDIR. (From OE-Core rev: 1115426dc5ac0cc3292ce02f687ba9297e643ef2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysdwarfsrcfiles: Switch to S = UNPACKDIRRichard Purdie
Since the recipe uses a single source file, use UNPACKDIR = ${S}. (From OE-Core rev: 77c2cc233be77a08a358063428bb669b55df5755) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayssdk: Fix path length limit to match reserved sizeRobert Kovacsics
(From OE-Core rev: 0f39a70c8f97867db279e05b132992c8736d3414) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 dayspopulate_sdk_ext.bbclass: Fix undefined variable errorJookia
The variable uninative_checksum is returned without being set, causing a build error. Set it to None by default instead. (From OE-Core rev: 6cafef695e5247465115d95740f8580176d3ef17) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysenchant2: Disable incompatible-pointer-types warning as errorKhem Raj
This fixes build with GCC-14 (From OE-Core rev: dc8c8ce6a293dd7c13ae79ee09e8e5fa28aaceca) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 daysgcc: Allow using libc++Dan McGregor
With the addition of the C++ runtime setting added recently, allow gcc to use libc++ as its runtime. There's some minor fixes still required, such as allowing setting the unwinder library. But this allows for testing libc++ with gcc. (From OE-Core rev: 49422ae16c23d00622cca6253120303fc0aaa550) Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>