Recommend libcomposite and usb_f_fs from the adbd package.
adbd needs both loaded: android-gadget-setup modprobes the first, and
the second comes in via request_module when the ffs function is
created. Nothing in an image pulls them in, so adbd fails to start on
kernels that build them as modules. A kernel with gadget support built
in ships no kernel-module packages, which recommendations tolerate.
Assisted-by: Claude Code:claude-opus-5
Signed-off-by: Daiane Angolini <daiane.angolini@oss.qualcomm.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Release notes:
* https://github.com/msgpack/msgpack-c/releases/tag/cpp-9.0.0
2026-08-25 version 9.0.0
Add regression tests for the fixes below. (#1183)
Fix ext_ref comparison operators ignoring the last payload byte. (#1183)
Fix out-of-bounds write on self-move-assignment of the create object visitor. (#1183)
Fix broken array_ref<T[N]> comparison operators. (#1183)
Fix heap buffer overflow in vrefbuffer::migrate() caused by a wrong growth check. (#1183)
Fix v1 unpacker not applying str/bin/ext size limits on the reference path. (#1183)
Fix x3 parser treating uint8 values as negative integers. (#1183)
Fix double free / use-after-free in zone::swap() (C++03 only). (#1183)
Fix use-after-free from wrong member destruction order in zone move-assignment. (#1183)
Fix use-after-free after moving an unpacker (dangling referenced buffer hook). (#1183)
Fix out-of-bounds read converting a short STR into std::array<char, N> / <unsigned char, N>. (#1183)
Fix out-of-bounds read and null dereference converting an array whose size differs from the tuple arity. (#1183)
Fix null pointer dereference converting an empty array into a C array T[N]. (#1183)
Fix integer overflow in the unpacker buffer expansion size arithmetic. (#1183)
<< breaking changes >>
Fix ext32 max size truncation on 64bit by widening visit_ext size to size_t. (#1183)
* If you have a custom visitor that implements visit_ext(), widen its size parameter from uint32_t to std::size_t:
Before: bool visit_ext(const char* v, uint32_t size)
After : bool visit_ext(const char* v, std::size_t size)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Without any prefix/suffix, it picks the highest version-like string.
Set REGEX to pick msgpack-cpp version.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
By default it picks the highest version, which for this repository is
for msgpack-cpp. Set GITTAGREGEX to pick msgpack-c tag.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
run-ptest piped ctest output through 'sed -u', which busybox sed does
not support, so the pipeline produced no output and the ptest image
reported "ptests which had no test results: ['jsoncpp']".
Drop sed and classify ctest result lines in awk directly. This also
maps Timeout/Exception/Not Run results to FAIL; previously they were
printed as e.g. "Exception:: <name>" and ignored by the ptest parser.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
OpenSSL 4.0 removed the ENGINE API. <openssl/engine.h> still exists as a
source-compatibility stub, so both binaries fail to link:
ld.lld: error: undefined symbol: ENGINE_load_builtin_engines
ld.lld: error: undefined symbol: ENGINE_by_id
ld.lld: error: undefined symbol: ENGINE_init
ld.lld: error: undefined symbol: ENGINE_ctrl_cmd_string
ld.lld: error: undefined symbol: ENGINE_load_public_key
The ENGINE use is confined to the "pkcs11:" input branch of each tool, so
compile that branch out on OpenSSL 4 and diagnose the unsupported input
instead. Reading certificates and public keys from PEM files, which is
what the kernel build and most other users do, is unaffected.
Providers supersede engines, but none exposes an equivalent of the pkcs11
engine's LOAD_CERT_CTRL command, so there is nothing to port to yet.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <raj.khem@gmail.com>
mercurial's setup.py treats ssl.HAS_TLSv1_2 as authoritative and refuses
to build at all:
The `ssl` module does not advertise support for TLS 1.2.
Please make sure that your Python installation was compiled against an
OpenSSL version enabling these features (likely this requires the
OpenSSL version to be at least 1.0.1).
ERROR: mercurial-7.2.4-r0 do_compile: Execution of .../run.do_compile
failed with exit code 1
Add a patch which only trusts the flag with OpenSSL < 4.0, in setup.py
and in sslutil.supportedprotocols (which otherwise loses b'tls1.2' and
makes `hg debuginstall` under-report the available protocols).
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Release notes:
https://github.com/microsoft/GSL/releases/tag/v5.0.0
Switch to the rel/5.0 branch. New in this release is the gsl::dyn_array
container, so the -dev package gains include/gsl/dyn_array.
Fix the build with clang 22. The tests are compiled with -Weverything
-Werror, so every new clang diagnostic becomes a build failure; the newly
added lifetime-safety suggestions produce:
notnull_tests.cpp:63:19: error: parameter in intra-TU constructor should
be marked [[clang::lifetimebound]]
[-Werror,-Wlifetime-safety-intra-tu-constructor-suggestions]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The wrapper script previously did not allow to instantiate templated
services without DefaultInstance defined. This change allows
foo@.service be installed and therefor be in enabled state.
In real systemd land, templated units without a specified instance are
valid, but we restrict it here a bit in order to not have a foo@.service
with:
[Install]
WantedBy=bar.service # bar.service starts -> start foo@???.service
In this case, system can never resolve the specific instance of
foo@.service when bar.service is started. It is fixed by adding the
template_only variable, which restricts the dependents of generic
template units to template-only ones. This means the following is still
legal for the above foo@.service:
[Install]
WantedBy=bar@.service # bar@1.service starts -> start foo@1.service
# bar@2.service starts -> start foo@2.service
# etc...
WantedBy=bas@1.service # bas@1.service starts -> start foo@1.service
# bas@2.service starts -> no dependency here
# etc...
Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Add two new recipes from the CentOS Automotive SIG
boot-time-analysis-tools project to enable boot time profiling
and measurement.
boot-time-analysis-tools:
Python-based toolset for collecting, analyzing and visualizing system
boot timing data from the systemd journal. Provides the 'boot_timings'
CLI utility which queries D-Bus and the systemd journal to produce
structured boot time reports. Depends on python3-dbus and python3-systemd
for runtime journal and D-Bus access.
cntvct-log:
Userspace C utility built with Meson that logs ARM CNTVCT_EL0 virtual
counter timestamps to correlate hardware-level timing with systemd boot
events. Installs cntvct@.service as a systemd template unit (disabled
by default) for on-demand per-instance activation. The service preset
file (98-cntvct-log.preset) is installed for system-preset-based enablement.
Both recipes fetch from the same upstream git repository:
https://gitlab.com/CentOS/automotive/src/boot-time-analysis-tools
Signed-off-by: Chitti Babu Theegala <ctheegal@qti.qualcomm.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Clang 23 renamed ASTContext::getRawCommentForDeclNoCache to
getRawCommentNoCache, so castxml no longer builds:
src/Output.cxx:1976:47: error: 'const class clang::ASTContext' has no
member named 'getRawCommentForDeclNoCache'; did you mean
'getRawCommentNoCache'?
Backport the upstream fix. It is guarded on LLVM_VERSION_MAJOR so older
Clang keeps working. There is no release carrying it yet; v0.7.0 is
still the newest tag.
Co-authored-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Sunil Dora <sunilkumar.dora@windriver.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Remove assignments to PYPI_PACKAGE where the value is the default value,
that is the recipe name with any python3- prefix removed.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The recipe produces static archives only, and does not compile them PIC, so
linking capnp or kj into a shared library fails:
libkj.a(exception.c++.o): relocation R_X86_64_TPOFF32 against
`kj::(anonymous namespace)::threadLocalCallback' can not be used when making
a shared object; local-exec is incompatible with -shared
kj/exception.c++ has a file-scope thread_local, which non-PIC code compiles to
the local-exec TLS model. A shared object cannot use that model, so the link
fails on any consumer that puts capnp inside a .so. Debian and Fedora do not
hit this because they ship shared libcapnp.
Set CMAKE_POSITION_INDEPENDENT_CODE. Packaging is unchanged: still static,
still no .so, no new packages and no ABI surface, only the code model differs.
Signed-off-by: Joel Winarske <joel.winarske@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
ldns implements GOST exclusively through the OpenSSL ENGINE API, which was
removed in OpenSSL 4.0
Causes
./keys.c:664:5: error: use of undeclared identifier 'ldns_key_new_frm_fp_gost_l'
664 | ldns_key_new_frm_fp_gost_l(fp, line_nr));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
USE_GOST gets defined because configure probes for a
working GOST engine using AC_RUN_IFELSE, which cannot run when cross
compiling and therefore falls back to "maybe", which is treated as success.
Pass --disable-gost since the feature cannot work at all without ENGINE
support.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
mkbootimg.py is used for creating boot.img for devices with abl
(android bootloader) like Qualcomm qcs8550 and similar.
Signed-off-by: Claus Stovgaard <claus@stovgaard.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
configgen.py writes the absolute path of config.xml into the header of
every file it generates, so generated_src/configvalues.h, which is
shipped in the doxygen-src package, carries the recipe build directory:
WARNING: doxygen-1.18.0-r0 do_package_qa: QA Issue: File
/usr/src/debug/doxygen/1.18.0/generated_src/configvalues.h in package
doxygen-src contains reference to TMPDIR [buildpaths]
On builders whose HOME is a parent of the build tree the same file e.g.
yocto autobuilder, also trips the build-host HOME variant of the check.
flex leaks the path of the lex file the same way: it emits a #line
directive for the %top{} block even when called with --noline, and
post_lex.py rewrites it to the absolute path of the original .l file.
Those .cpp files are not shipped today, but the leak is the same one.
Strip ${B}/ and ${S}/ from everything under generated_src/ during
do_install, before do_package picks the sources up, so the references
become relative.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
OpenSSL 4.0 returns const pointers from X509 accessor functions,
makes ASN1_OCTET_STRING opaque, and deprecates HMAC one-shot API.
Four patches addressing credentials, TSI transport security, and
TSI utils.
Upstream-Status: Submitted [https://github.com/grpc/grpc/pull/41932]
Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The default product-only mapping generates a vendor-wildcard CPE.
nlnetlabs:ldns is the active NVD dictionary CPE and configuration
identity for the packaged NLnet Labs source.
This changes the generated product identity to an exact CPE, but the
frozen sbom-cve-check database leaves the eight-entry CVE report
unchanged, with no current CVE delta.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The default product-only mapping generates a vendor-wildcard CPE.
Use jq_project:jq for the historical NVD dictionary CPE and configuration
identity carrying two jq 1.5 CVEs, and jqlang:jq for the active NVD
dictionary CPE and configuration identity plus CNA affected-data identity
used by the current upstream.
This changes the generated identities to two exact CPEs, but the frozen
sbom-cve-check database leaves the 26-entry CVE report unchanged, with no
current CVE delta.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The default product-only mapping generates a vendor-wildcard CPE. php:php
is the active NVD dictionary CPE and configuration identity. php_group:php
preserves historical NVD configurations and current authoritative PHP
Security CNA affected data for the same php-src source; it is not an NVD
dictionary CPE.
This changes the generated identities to two exact CPEs, but the frozen
sbom-cve-check database leaves the 731-entry CVE report unchanged, with no
current CVE delta.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
All 6 ptest failures (t/31methcache, t/35thrclone, t/40profile,
t/41prof_dump, t/42prof_data, t/43prof_env) are missing runtime perl
modules, in two groups:
Module::Load, required by DBI/Profile.pm line 682:
Can't locate Module/Load.pm in @INC ... at
/usr/lib/perl5/vendor_perl/5.44.0/aarch64-linux/DBI/Profile.pm line 682.
This breaks t/40profile and t/43prof_env directly, and cascades into
t/41prof_dump and t/42prof_data: once DBI/Profile.pm fails to compile,
%INC is poisoned, so those two report "Attempt to reload DBI/Profile.pm
aborted" and a missing DBI::Profile->flush_to_disk method rather than
the underlying cause. Provided by perl-module-load.
Test2::Util::Sig, required by Test2/IPC/Driver/Files.pm line 18, which
Test::Builder pulls in when a test enables Test2 IPC (threads/forking):
Can't locate Test2/Util/Sig.pm in @INC ... at
/usr/lib/perl5/5.44.0/Test2/IPC/Driver/Files.pm line 18.
This makes Test::More unusable in t/31methcache and t/35thrclone, which
is why only those two of the many Test::More-based tests fail. Provided
by perl-module-test2-util-sig.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
SuiteSparse adds -Wl,-rpath=$(INSTALL_LIB) while linking shared
libraries on Linux. In the OpenEmbedded build this value can resolve to
a build or install path under TMPDIR, so installed ELF files can keep an
absolute build path and fail buildpaths QA.
The packaged libraries do not need this install-tree rpath. Runtime
resolution is handled through normal package dependencies and the target
library search path. Keep the librt link and drop only the rpath entry.
Signed-off-by: Himanshu Jadon <hjadon@cisco.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
SuiteSparse 5.10.1 still carries bundled CMake entry points with
2.x minimum versions. CMake 4 rejects projects which request
compatibility with versions older than 3.5, so configure fails before
SuiteSparse can build.
Backport the upstream SuiteSparse change which raises the bundled
Mongoose, METIS and GKlib minimum version to 3.13. This version also
reaches two bundled GraphBLAS CMake entry points with the same old
minimum, so update those in the backport as well.
Signed-off-by: Himanshu Jadon <hjadon@cisco.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
glib-mkenums records the "enumerations from" comment using the
input file's full path (@filename@), embedding the build host's
TMPDIR/HOME path into the installed gladeui-enum-types.c/.h and
tripping the buildpaths QA check:
WARNING: glade-3.40.0-r0 do_package_qa: QA Issue: File
/usr/src/debug/glade/3.40.0/gladeui/gladeui-enum-types.c in
package glade-src contains reference to TMPDIR [buildpaths]
Switch both mkenums templates to @basename@ (supported since glib
2.22), the same fix already used for the analogous gcab-enums
issue. Verified with a clean rebuild: do_package_qa now reports no
buildpaths warnings for glade.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Release Notes: https://github.com/google/perfetto/releases/tag/v57.2
perfetto 57.2 added a new build-time dependency on RE2 (via
enable_perfetto_re2, unconditionally true for standalone builds) for trace
processor regex support, so a matching buildtools/re2 git fetch/SRCREV was
added to perfetto.bb, mirroring the existing buildtools/* pattern from
tools/install-build-deps. abseil-cpp is now fetched the same way for the
same reason.
Upstream also dropped the amalgamated sdk/perfetto.{h,cc} from the git
release branches (now shipped only as a GitHub release .zip asset), so
libperfetto.bb now fetches perfetto-cpp-sdk-src.zip and unpacks it into
sdk/, which the meson build requires.
Build-verified for qemux86-64: both perfetto and libperfetto build
through do_package_qa cleanly.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Minor release. Dropped 0001-setup.py-Disable-autodection-of-modules.patch:
2.13's setup.py already passes both packages=[] and py_modules=[] itself, so
re-adding py_modules=[] produced a "keyword argument repeated" SyntaxError.
Rebased 0001-unattended-upgrade-Remove-distro_info-usage-to-check.patch onto
the new import block and the shifted run() body.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Point release. Two patches needed rebasing:
0009-Using-native-binaries.patch's context shifted because upstream added
its own '<@(emulator)' gyp variable (defaults to empty in common.gypi) to a
couple of the same action arrays this patch touches; this recipe never sets
GYP_DEFINES emulator=..., so it stays empty and our v8-qemu-wrapper.sh
insertion is unaffected either way. 0007-positional-args.patch's single-line
shebang fix (bash -> sh) was already applied on top of an unrelated wording
change upstream made to the same 3-line fixture file, just offset by one
line (context-only).
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Minor release. Two recipe-side fixes needed for the new meson.build:
3.40.0 renamed the "docs" option to "gtk_doc" and dropped "introspection"
entirely (introspection is no longer optional), so gtk-doc.bbclass and
gobject-introspection.bbclass are repointed via GTKDOC_MESON_OPTION and
GIR_MESON_OPTION rather than guessing at PACKAGECONFIG. 3.40.0 also ships
new /usr/share/help (translated user docs) and /usr/share/gettext/its
(catalog ITS rules) content that the old FILES:${PN} didn't claim, added.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Point release from oe-core gstreamer1.0 1.28.x. SRC_URI[sha256sum] filled in for the new tarball.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>