Mirror of git.openembedded.org/meta-openembedded https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=master-next 2026-03-18T21:33:27+00:00 2026-03-18T21:33:27+00:00 Gyorgy Sarvari skandigraun@gmail.com 2026-03-16T12:21:29+00:00 urn:sha1:c407d8669caea716d19f026112eb6419edd94364 Contains fix for CVE-2026-32239 and CVE-2026-32240 Also, mark these CVEs explicitly patched, because NVD tracks them without version info at this time. Shortlog: https://github.com/capnproto/capnproto/compare/v1.0.2...v1.4.0 Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2025-06-25T13:44:52+00:00 Alexander Kanavin alex@linutronix.de 2025-06-20T14:06:53+00:00 urn:sha1:fc78d37ff0ce9e0d60455465851dbe4e86d7a8b3 Please see https://git.yoctoproject.org/poky/commit/?id=4dd321f8b83afecd962393101b2a6861275b5265 for what changes are needed, and sed commands that can be used to make them en masse. I've verified that bitbake -c patch world works with these, but did not run a world build; the majority of recipes shouldn't need further fixups, but if there are some that still fall out, they can be fixed in followups. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2025-02-25T17:46:52+00:00 Gyorgy Sarvari skandigraun@gmail.com 2025-02-25T13:33:35+00:00 urn:sha1:e3c5b2dd0c5758da6396514c6c6ec413056b6fe0 The base problem this is trying to solve: capnproto has two main components: libraries that can be linked against, and binary files that can generate c++ code from capnproto definitions. When cross-compiling one needs to use the cross-compiled libraries, but with the native definition-compilers. When linking against capnproto from another recipe, cross-compilation fails, because the cmake files generated by capnproto verify the existence of binary files in $bindir. When using a cross-compiled version of capnproto, these binary files do not exist in RECIPE_SYSROOT, so the compilation fails. The previous patch: the previous solution patched the CMakeLists.txt file in a way that it didn't export nor install the generated binary files. Accidentally this also happened with native build (and happened knowingly with target builds). The new patch: instead of not installing and not exporting the binaries, just install them without exporting, when creating a target build. During compilation check is CMAKE_CROSSCOMPILING is set (coming from cmake.bbclass) - if it is set, only install the binaries, without exporting. When it is not set, resort to the original behavior. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2025-02-03T19:25:22+00:00 Gyorgy Sarvari skandigraun@gmail.com 2025-02-03T12:10:23+00:00 urn:sha1:6b1ba4543a2576ef3d83306190a188b6083e6c9e When linking to capnproto from another project, cmake fails to find this package with the following error: | CMake Error at ${RECIPE_SYSROOT}/usr/lib/cmake/CapnProto/CapnProtoTargets.cmake:176 (message): | The imported target "CapnProto::capnp_tool" references the file | | "${RECIPE_SYSROOT}/usr/bin/capnp" | | but this file does not exist. Possible reasons include: To solve this, this change includes the following: 1. Add a patch that removes the files installed (and exported) in ${bindir} from the target build. The CMake file originally verified that these files exist when another recipe tried to use it, however the ${RECIPE_SYSROOT} does not contain the binaries in ${bindir}, so it failed quick in the do_configure step. (This alone is enough to link against the cross-compiled libraries of capnproto successfully, but code-generation from capnproto definition fails) 2. Add a new bbclass for capnproto. To cross-compile an application that uses capnproto, the application needs to be linked against the cross-compiled version of the libraries, however the native version of the binaries need to be used to generate C++ code from the capnproto definitions. This class sets the correct CMake arguments, to use the capnproto binaries from the native package, instead of looking for the non-existent cross-compiled binaries. (These variables can be found in ${libdir}/cmake/CapnProto/CapnProtoConfig.cmake file) Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2024-09-26T13:58:28+00:00 s-tokumoto s-tokumoto@fujitsu.com 2024-09-26T10:50:49+00:00 urn:sha1:624544ac41934949054a5d2a58acbb45266f2105 Vulnerabilities against capnproto are sometimes reported as "capnp", so add "capnp" to CVE_PRODUCT. https://nvd.nist.gov/vuln/detail/CVE-2022-46149 Signed-off-by: Shunsuke Tokumoto <s-tokumoto@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2024-01-23T19:55:34+00:00 Wang Mingyu wangmy@fujitsu.com 2024-01-23T01:12:54+00:00 urn:sha1:c1e3429d596afc0a066b6c0f66cbd214f7062f12 Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2023-11-28T16:55:40+00:00 Wang Mingyu wangmy@fujitsu.com 2023-11-28T08:18:46+00:00 urn:sha1:5c9927db548496dba06cd76c324ea9e8c056348c Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2023-11-17T19:38:25+00:00 alperak alperyasinak1@gmail.com 2023-11-16T16:35:24+00:00 urn:sha1:dbee6afc11686501e9f9866d623d24e3ff440006 Signed-off-by: alperak <alperyasinak1@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2023-04-17T16:53:31+00:00 Wang Mingyu wangmy@fujitsu.com 2023-04-17T07:38:02+00:00 urn:sha1:24d8984345e9f5bf27f0dd1f3148b59c33a40424 Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2022-12-05T17:16:24+00:00 Wang Mingyu wangmy@fujitsu.com 2022-12-03T11:12:54+00:00 urn:sha1:bfd2ea6cdc011996435749dd5068c486d224dd5e Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>