summaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
* nodejs: Delete clang libatomic patchKhem Raj2026-06-072-96/+0
| | | | | | | This patch is not right and moreover not needed anymore with latest clang Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jemalloc: add backport patch to fix build with gcc 16Markus Volk2026-06-072-0/+159
| | | | | | | This patch replaces std::__throw_bad_alloc call with standard C++ Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jsoncpp: add a backport patch to fix build with gcc16Markus Volk2026-06-072-0/+64
| | | | | | | | | | | Partially backport https://github.com/open-source-parsers/jsoncpp/commit/71d46ca38e90dc902e8178ba484af4f27fa11947.patch This fixes build with gcc 16 Upstream-Status: Backport [https://github.com/open-source-parsers/jsoncpp/commit/71d46ca38e90dc902e8178ba484af4f27fa11947] Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jq: patch CVE-2026-47770Anton Skorup2026-06-072-0/+485
| | | | | | | | | This patch adds the upstream fix for CVE-2026-47770. CVE details: https://ubuntu.com/security/CVE-2026-47770 Signed-off-by: Anton Skorup <antonsk@axis.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* microsoft-gsl: upgrade 4.2.1 -> 4.2.2Wang Mingyu2026-05-311-1/+1
| | | | | | | | Changelog: Fix MSVC's C4875 when compiling GSL 4.2.1 with latest MSVC toolset. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* ctags: upgrade 6.2.20260510.0 -> 6.2.20260524.0Wang Mingyu2026-05-311-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* android-tools: fix deprecated header warning from clangAshishKumar Mishra2026-05-241-6/+9
| | | | | | | | | | | | Remove .h header files from the SOURCES compilation list inside adbd.mk to resolve a Clang warning regarding treating 'c-header' input as 'c++-header' Moved the header files into a separate HEADERS variable to act purely as a GNU Make dependency trigger, keeping them off the direct compiler execution string. Signed-off-by: AshishKumar Mishra <ashishkumar.mishra@bmwtechworks.in> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* android-tools: removes selinux dependency from android-tools_29.0.6.r14.bbAshishKumar Mishra2026-05-241-1/+4
| | | | | Signed-off-by: AshishKumar Mishra <ashishkumar.mishra@bmwtechworks.in> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* android-tools: move android-tools v29.x from dynamic-layers/selinux to meta-oeAshishKumar Mishra2026-05-2452-0/+3831
| | | | | | | | | | | | | | | | | | | Relocate the recipe from dynamic-layers/selinux/ to the main meta-oe/recipes-devtools/ directory. The android-tools recipe (version 29.0.6.r14) was previously restricted to the selinux dynamic-layer. Investigation shows that version 29.0.6.r14 does not have a hard dependency on libselinux for core tool functionality. (adb, fastboot, and sparse image tools). - Basic runable test was done for binaries in android-tools-native - Checked for selinux absense by looking for selinx using $ ldd binary-name Changes: - Relocate recipe from dynamic-layers/selinux/ to recipes-devtools/ Signed-off-by: AshishKumar Mishra <ashishkumar.mishra@bmwtechworks.in> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* android-tools: remove android-tools 5.x from meta-oe/recipes-devtoolsAshishKumar Mishra2026-05-2441-3473/+0
| | | | | | | | We plan to upgrade android-tools from the legacy 5.1.1 version to 29.0.6.r14 To achive this we are removing the older version from meta-oe/recipes-devtools/ Signed-off-by: AshishKumar Mishra <ashishkumar.mishra@bmwtechworks.in> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* nodejs: upgrade 22.22.3 -> 24.16.0 (LTS)Tim Orling2026-05-2114-232/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add Node.js 24.16.0 [1] recipe based on 22.22.3. Patches reviewed against the 24.15.0 source tree and rebased where needed: - 0001: rebased for Makefile changes (common_node.gypi removed, line offsets shifted); merged with Disable-running-gyp-files patch since both modify the same Makefile hunk. Remove deps/simdutf/simdutf.gyp; no longer vendored here. - 0005: rebased for v8.gyp libatomic condition change (clang condition folded upstream, ppc removed) - v24.16.0 bumps bundled llhttp to 9.3.1 (LLHTTP_VERSION_MAJOR/MINOR/PATCH = 9/3/1 in deps/llhttp/include/llhttp.h). Five patches dropped as no longer needed: - build-remove-redundant-mXX-flags-for-V8: backport already merged upstream in Node.js 24 - ppc64-Do-not-use-mminimal-toc-with-clang: Node.js 24 common.gypi already gates -mminimal-toc behind clang==0 - fix-arm-Neon-intrinsics-types: the v24.16.0 source already uses vandq_u8/vorrq_u8 and vshrn_n_u16(vreinterpretq_u16_u8(mask), 4). - detect-aarch64-Neon-correctly: #ifdef __ARM_NEON__ → #if defined(__ARM_NEON__) || defined(__ARM_NEON) — already present at lines 13 and 2628. - llhttp-fix-NEON-header-value-__builtin_ctzll-undefin: wanted the match_mask == 0 guard around __builtin_ctzll — already present. "This patch can be dropped when nodejs updates its bundled llhttp to >= 9.3.1.") Remaining 9 patches renumbered sequentially 0001-0009. All verified to apply cleanly against the v24.16.0 source tarball. NOTE: The "current" release is v26.2.0 [1], but this is not yet an LTS release. Application stacks frequently lag new releases, so it makes sense to have support for the v24 LTS release. [1] https://nodejs.org/en/blog/release/v24.16.0 [2] https://nodejs.org/en/blog/release/v26.2.0 Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* nodejs-oe-cache-native: upgrade to version 24.16Tim Orling2026-05-212-0/+0
| | | | | | | | Add oe-cache recipe for Node.js 24.16, replacing the existing 22.22 version. This provides the npm cache helper used during SDK builds. Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jemalloc: fix version stringYi Zhao2026-05-211-1/+1
| | | | | | | | Referring to the VERSION file within the released source tarball, the version string for --with-version option should be ${PV}-0-g${SRCREV}. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* ctags: upgrade 6.2.20260426.0 -> 6.2.20260510.0Wang Mingyu2026-05-201-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* nodejs: upgrade 22.22.2 -> 22.22.3Jason Schonberg2026-05-144-174/+1
| | | | | | | | | | With this upgrade, nodejs updated the llhttp dependency to version 9.3.1 So some of the patches are nolonger necessary. Changelog: https://github.com/nodejs/node/releases/tag/v22.22.3 Signed-off-by: Jason Schonberg <schonm@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jsoncpp: Fix C++11 ABI breakage when compiled with C++17Ernest Van Hoecke2026-05-132-0/+369
| | | | | | | | | | | | | | | When jsoncpp is built with C++17, 1.9.7 drops several legacy overloads that C++11 consumers can still link against. Backport the upstream fix to restore compatibility. Fixes errors such as: | undefined reference to `Json::Value::operator[](char const*)' Patch can be dropped when we move to 1.9.8. Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@toradex.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* exiftool: upgrade 13.57 -> 13.58Wang Mingyu2026-05-131-1/+1
| | | | | | | | | | | | | | | | | | Changelog: =========== - Added a few new Nikon Z lenses - Added a few new QuickTime MajorBrand values - Added a new RAFCompression value - Added undocumented -eh option (alias for -E/-escapeHTML) - Decode timed GPS from INNOVV N2 TS videos - Improved decoding of Canon ColorData for some models - Changed the name of the RAFVersion tag to FirmwareVersion - Removed conversion for Garmin FIT DeviceIndex values - Properly parse XML CDATA and comment sections - Fixed issue which could cause failed Garmin test on some systems Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* doxygen: upgrade 1.16.1 -> 1.17.0Wang Mingyu2026-05-131-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* php: upgrade 8.5.5 -> 8.5.6Jason Schonberg2026-05-131-1/+1
| | | | | | | | | This is a security release. Changelog: https://www.php.net/ChangeLog-8.php#8.5.6 Signed-off-by: Jason Schonberg <schonm@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jemalloc: upgrade 5.3.0 -> 5.3.1Wang Mingyu2026-05-121-4/+2
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* isocline: upgrade 1.0.9 -> 1.1.0Wang Mingyu2026-05-121-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* ctags: upgrade 6.2.20260329.0 -> 6.2.20260426.0Wang Mingyu2026-05-071-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* exiftool: upgrade 13.52 -> 13.57Liu Yiding2026-05-071-1/+1
| | | | | | | | 1. ChangeLog https://github.com/exiftool/exiftool/blob/master/Changes Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* editorconfig-core-c: upgrade 0.12.9 -> 0.12.11Liu Yiding2026-05-071-3/+3
| | | | | | | | | | 1. ChangeLog https://github.com/editorconfig/editorconfig-core-c/releases/tag/v0.12.11 2. Fix HOMEPAGE Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jemalloc: fix always_inline build failureXiaozhan Li2026-04-231-0/+2
| | | | | | | | | Enable debug build flag in jemalloc to avoid error as below: inlining failed in call to 'always_inline' 'heap_ph_cmp': function not considered for inlining Signed-off-by: Xiaozhan Li <Xiaozhan.Li.CN@windriver.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* protobuf, python3-protobuf: ignore CVE-2026-6409Gyorgy Sarvari2026-04-201-0/+1
| | | | | | | | | | Details: https://nvd.nist.gov/vuln/detail/CVE-2026-6409 The vulnerability impacts only the PHP library component, not the cpp/python one. Ignore this CVE due to this. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jq: patch CVE-2026-39979Gyorgy Sarvari2026-04-202-0/+32
| | | | | | | | | Details: https://nvd.nist.gov/vuln/detail/CVE-2026-39979 Backport the patch that is referenced by the NVD advisory.y Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jq: patch CVE-2026-33948Gyorgy Sarvari2026-04-202-0/+50
| | | | | | | | | Details: https://nvd.nist.gov/vuln/detail/CVE-2026-33948 Backport the patch that is referenced by the NVD advisory. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jq: patch CVE-2026-33947Gyorgy Sarvari2026-04-202-0/+105
| | | | | | | | | Details: https://nvd.nist.gov/vuln/detail/CVE-2026-33947 Backport the patch that is referenced by the NVD report. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jq: patch CVE-2026-32316Gyorgy Sarvari2026-04-202-5/+58
| | | | | | | | | Details: https://nvd.nist.gov/vuln/detail/CVE-2026-32316 Backport the patch that is referenced by the NVD advisory. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* libtoml11: Fix build with C23 and clangKhem Raj2026-04-172-0/+37
| | | | Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* lshw: Fix binmergeJörg Sommer2026-04-151-2/+2
| | | | | | | In case $sbindir = $bindir we have to pass this setting to make. Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jsoncpp: add ptest supportZeming LIU2026-04-152-6/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | Add ptest support for jsoncpp to enable automated testing of the JSON C++ library functionality. Note: - Tested on: WRLinux master-wr (based on meta-openembedded master) - jsoncpp version: 1.9.7 - Unable to test on pure upstream due to poky/meta-oe branch mismatch Test Result: root@qemux86-64:~# ptest-runner jsoncpp START: ptest-runner 2026-04-15T14:04 BEGIN: /usr/lib64/jsoncpp/ptest PASS: jsoncpp_readerwriter PASS: jsoncpp_readerwriter_json_checker PASS: jsoncpp_test DURATION: 122 END: /usr/lib64/jsoncpp/ptest 2026-04-15T14:06 STOP: ptest-runner TOTAL: 1 FAIL: 0 Signed-off-by: Zeming LIU <zeming.liu@windriver.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* mpich: upgrade 5.0.0 -> 5.0.1Wang Mingyu2026-04-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Changelog: ========== - Fix bad cast in release-gather collectives that caused data loss issues on Big-Endian 64b arches (s390x) - Fix issue with canceling MPI_ANY_SOURCE receive requests - Fix configuration issue when C++ compiler does not support complex types - Fix function signature issue in Hydra PBS support - Fix crash in MPI_Allreduce with MPI_LOGICAL type - Fix potential crash in multi-nic libfabric initialization - Fix memory leaks in Level Zero and PMIx support - Fix bug in CMA code when GPU support is enabled - Fix potential shared memory collision between multiple singleton processes on the same node - Add large count and other necessary aliases to ROMIO to avoid accidental profiling of internal MPI function usage - Add missing error checks in rndv and colletive composition code - Improve autogen.sh error message when autotools are too old Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* b4: upgrade 0.15.1 -> 0.15.2Wang Mingyu2026-04-141-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* xerces-c: fix escaping in CVE_PRODUCTRoss Burton2026-04-141-1/+1
| | | | | | | | | | The CPE parsing in oe-core's cve_check.py now handles escapes correctly[1] so we don't need to escape in CVE_PRODUCT. [1] oe-core 3c73dafd03b ("cve_check: Improve escaping of special characters in CPE 2.3") Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* nodejs: mark CVE-2026-21710 patchedGyorgy Sarvari2026-04-131-0/+1
| | | | | | | | | | | | | | Details: https://nvd.nist.gov/vuln/detail/CVE-2026-21710 The CVE is fixed in the current recipe version[1], but NVD tracks it without verison info. Mark it as patched in the recipe. [1]: https://github.com/nodejs/node/blob/v22.x/doc/changelogs/CHANGELOG_V22.md Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* ltrace: Upgrade to 0.8.1 and clang build errorsKhem Raj2026-04-125-119/+125
| | | | | | | | Drop the upstream applied patches Add patches to fix build with clang-22 Bump PE to account for version going from 7.x to 0.8 Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* php: upgrade 8.5.4 -> 8.5.5Jason Schonberg2026-04-101-1/+1
| | | | | | | | | This is a bug fix release. Changelog: https://www.php.net/ChangeLog-8.php#8.5.5 Signed-off-by: Jason Schonberg <schonm@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* protobuf-c: upgrade 1.5.1 to 1.5.2Changqing Li2026-04-102-1448/+1
| | | | | | | | | | | | | Changes[1]: * Chase compatibility issues with Google protobuf 30.0-rc1 by @edmonds in https://github.com/protobuf-c/protobuf-c/pull/762 * protoc-gen-c: Explicitly construct strings where needed for protobuf 30.x by @edmonds in https://github.com/protobuf-c/protobuf-c/pull/768 Remove protobuf-30.patch, this patch already included in 1.5.2 [1] https://github.com/protobuf-c/protobuf-c/compare/v1.5.1...v1.5.2 Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* jq: Use Git to fetch the codePeter Kjellerstedt2026-04-102-6/+52
| | | | | | | | | | | | | | | | | There is a bug (see https://github.com/jqlang/jq/issues/434), which results in an empty version being used if autoreconf is run on the jq sources when using a release tar ball. The incorrect assumption is that autoreconf is only used when fetching the code using Git. The empty version results in an incorrect libjq.pc file being created where the version is not set, which results in, e.g., `pkgconf --libs 'libjq > 1.6'` failing even if version 1.8.1 of jq is actually installed. Switch to fetching the code using Git to workaround the bug. Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* nodejs: ignore fixed CVEsGyorgy Sarvari2026-04-061-0/+7
| | | | | | | | | | | | | All these CVEs are fixed in v22.22.2[1], except for CVE-2026-21712, which does not affect v22 series, because it was introduced in a later version[2]. All these CVEs are tracked without version info by NVD at the time of creating this patch. [1]: https://github.com/nodejs/node/blob/v22.x/doc/changelogs/CHANGELOG_V22.md [2]: https://nodejs.org/en/blog/vulnerability/march-2026-security-releases Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* giflib: mark CVE-2026-23868 patchedGyorgy Sarvari2026-04-061-0/+2
| | | | | | | | | | The fix[1] that is referenced by the NVD advisory is already included in the current recipe version. [1]: https://sourceforge.net/p/giflib/code/ci/f5b7267aed3665ef025c13823e454170d031c106/ Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* sip: upgrade 6.15.2 -> 6.15.3Wang Mingyu2026-04-011-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* debootstrap: upgrade 1.0.142 -> 1.0.143Wang Mingyu2026-04-011-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* ctags: upgrade 6.2.20260322.0 -> 6.2.20260329.0Wang Mingyu2026-04-011-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* b4: upgrade 0.15.0 -> 0.15.1Wang Mingyu2026-04-011-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* giflib: upgrade 5.2.2 -> 6.1.2Gyorgy Sarvari2026-04-012-37/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Drop patch that was merged upstream. License update: a copyright line was removed. The license is still MIT. Changes: Version 6.1.2 ============= Code Fixes ---------- * Fix for low-severity CVE-2026-23868 affecting gifponge, giftool, and gifbuild, but not the core library - library clients need not be alarned. Version 6.1.1 ============= This release bumps the major version, but only one entry point - EGifSpew() - has changed signature and behavior (in order to be able to pass out a detailed error code). The internal error codes in the E_GIF_ERR series have changed value so none of them collides with GIF_ERROR. This code has been systematically audited and hardened wuth ChatGPT-5.2. The only library fixes reported by users or found by robot were for some memory leaks that could only triggered by severely malformed GIFs. Other bugs are edge-case failures in the CLI tools. The gif2rbg CLI tool has been moved to the "obsolete" bin, because its only deployment case in 2026 is as a piñata at fuzzer parties. Warning: the CLI tools in the obsolete category will soon be removed from the distribution entirely. The maintainer is tired of fielding junk bugs filed against them by would-be coup-counters who found yet another edge case, and the rest of the world doesn't need noisy CVEs that aren't actually DoS or security issues for giflib clients. Code Fixes ---------- * Fix for CVE-2021-40633. * Fix SF bug #165 EGifSpew leaks GifFileOut->SColorMap * Fix SF bug #171 ImageMagick required to build giflib on non-Darwin Platforms * Fix SF bug #172 Incorrect object files in shared libutil on darwin * Fix SF bug #173 installation of manual pages and html documentation * Fix SF bug #175 Memory leaks in gifecho.c's main() and in gifalloc.c's GifMakeMapObject * Fix SF bug #177 wrong pointer used in giftool getbool * Fix SF bug #179 Path Traversal vulnerability * Fix SF bug #180: -Wformat-truncation likely pointing out an actual bug * Fix SF bug #182 out‐of‐bounds writes in Icon2Gif * Fix SF bug #184 uninitialized buffer in DumpScreen2RGB * Fix SF bug #185 integer overflow in gifbg.c * Fix SF bug #186 integer overflow in Icon2Gif * Fix SF bug #187: CVE-2025-31344 * Fix SF bug #170 Tests failing on Ubuntu Noble, giftext buffer overflow * Fix SF bug #165 EGifSpew leaks GifFileOut->SColorMap * Fix SF bug #162 detected memory leaks in GifMakeSavedImage giflib/gifalloc.c * Fix SF bug #161 detected memory leaks in EGifOpenFileHandle giflib/egif_lib.c * Fix SF bug #142 ABI break public symbol GifQuantizeBuffer Other bugs that duplicate these have breen addressesed by these fixes * SF bug #156 EGifSpew leaks SavedImages (and more); won't fix, caller might want to write a GIF, modify the in-memory data, then write again. Tests ----- Test suite now emits TAP (Test Anything Protocol). Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* canvenient: update to version 1.01Michael Fitzmayer2026-04-011-0/+41
| | | | | | | | | - Add versioning - New version to be able to use a proper version tag in the Yocto recipe Signed-off-by: Michael Fitzmayer <mail@michael-fitzmayer.de> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
* flatbuffers: Convert confusing append to override syntaxMichal Sieron2026-04-011-1/+1
| | | | | | | | | | While in this case `SYSROOT_PREPROCESS_FUNCS:class-target +=` wouldn't result in any unwanted override, there is no guarantee there won't be a change, which would be hidden by this override. To avoid any surprises in the future let's use `:append:class-target =` syntax here. Signed-off-by: Michal Sieron <michalwsieron@gmail.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>