This replaces the specific gtkdoc wrapper setting
(which was rejected by upstream in https://github.com/mesonbuild/meson/pull/9627)
with a generic, officially supported and documented exe_wrapper,
which is enabled subject to qemu usermode support
(just as is done for g-i and gtk-doc with autotools).
gtk-doc support is adjusted so that this wrapper is passed to
meson's gtk-doc module, which passes it to gtk-doc.
The adjusted patch is re-submitted upstream.
The side effect of this is that meson is now able to run
target binaries in a generic way when it wants to, so this
may affect cross-builds - hopefully in a positive way.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Jon Mason [Sat, 4 Dec 2021 18:18:09 +0000 (13:18 -0500)]
yocto-check-layer: disregard checks if referencing another README file
It is permissible to have a layer's README reference another README. If
this is the case, avoid other checks. Do this by checking for the word
README (case insensitive) in the README file. This might be too
permissive, but follows the pattern of looking for exact words (like
"patch" or "maintainer") in READMEs.
Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Dhruva Gole [Tue, 30 Nov 2021 05:43:35 +0000 (11:13 +0530)]
yocto-check-layer: Add additional README checks
This adds:
- Test case to review if the README file specifies the maintainer.
- Test case to review if the README file specifies the word patch.
- Test case to review if the README file contains an email address.
[YOCTO #11131]
Signed-off-by: Dhruva Gole <goledhruva@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pavel Zhukov [Thu, 2 Dec 2021 07:56:04 +0000 (08:56 +0100)]
patch.py: Initialize git repo before patching
If PATCHTOOL="git" has been specified but workdir is not git repo
bitbake fails to apply the patches with error message:
Command Error: 'git rev-parse --show-toplevel' exited with 0 Output:
fatal: not a git repository (or any of the parent directories): .git
Fix this by initializing the repo before patching.
This allows binary git patches to be applied.
Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj [Thu, 2 Dec 2021 06:19:33 +0000 (22:19 -0800)]
glibc: Drop patch to support/workaround prelinked apps on armv5
The usecase explained in bug #1443 works fine now a days on qemuarmv5,
tested by using lltng-ust and explicitly linking in liburcu-bp.so as
well, since its no more a direct dependency of liblttng-ust.so.1
Given that usecase works, unbolt this fix now.
Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Li Wang [Tue, 30 Nov 2021 06:51:11 +0000 (14:51 +0800)]
libtool: change the default AR_FLAGS from "cru" to "cr"
Backport patch to fix warning:
`u' modifier ignored since `D' is the default (see `U')
Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This breaks machines using fbdev backend, since this option is drm
backend specific, we need to know the backend before using it, until we
have a smart way to detect that, this will not be a fool proof solution,
therefore revert it for now.
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 29 Nov 2021 09:57:59 +0000 (17:57 +0800)]
python3-libarchive-c: upgrade 3.1 -> 3.2
This release fixes the seek callbacks passed to libarchive by the custom_reader and stream_reader function.
(https://github.com/Changaco/python-libarchive-c/pull/116)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 29 Nov 2021 09:57:58 +0000 (17:57 +0800)]
python3-docutils: upgrade 0.18 -> 0.18.1
Changelog:
docutils/nodes.py
Node.traverse() returns a list again to restore backwards compatibility. Fixes bug #431.
New method Node.findall(): like Node.traverse() but returns an iterator. Obsoletes Node.traverse().
docutils/utils/__init__.py:
Fix behaviour of get_stylesheet_list(): do not look up stylesheets given as "stylesheet" setting. Cf. bug #434.
docutils/writers/_html_base.py:
Fix handling of footnote_backlinks==False (report Alan G Isaac).
wangmy [Mon, 29 Nov 2021 15:01:45 +0000 (23:01 +0800)]
sysklogd: upgrade 2.2.3 -> 2.3.0
Changes:
Add support for logger -k, early log to /dev/kmsg. Useful when
logging from early system startup scripts before syslogd has started
Support for extracting non-kernel log messages from /dev/kmsg
Ignore EINVAL from kernel, caused warning message at first startup
Use journald socket on systemd systems, not /dev/log
Issue #38: add support for syslogd -C file to use file for caching
the last seen kernel sequence number, default: /run/syslogd.cache.
Note: syslogd relies on the location of this file to be wiped at
system boot. The default, /run, is a RAM disk on modern systems
Fixes
Issue #34: regression in v2.2.3, causing loss of syslogd log messages
like syslogd v2.2.3: restart.
Issue #35: man pages lists -v as verbose mode, is actually version
Issue #36: retry DNS lookup of remote syslog servers with res_init()
to ensure name resolution at bootup when a remote DNS may temporarily
be unreachable. Retry at most every five seconds, to prevent syslogd
from monopolizing the CPU when emptying the kernel ring buffer
Issue #39: update tests to use -P fn and -C fn
Issue #40: improve documentation for syslogd.cache file requirements
Issue #41: add missing documentation for -H option
Issue #42: add option (-K) to always trust kernel timestamp. By
default syslogd only trusts the kernel timestamp for the initial
emptying of the kernel ring buffer
Issue #43: avoid asserting (exiting) on and around Jan 19, 2038, when
the UNIX epoch wraps around on 32-bit time_t systems
libsyslog: handle EOVERFLOW from gettimeofday() on Jan 19, 2038
Avoid NULL pointers to internal logit() function, only triggered
when in debug mode
Replace \m with \n (missing newline) in logger usage text
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 29 Nov 2021 15:00:55 +0000 (23:00 +0800)]
sqlite3: upgrade 3.36.0 -> 3.37.0
Changelog:
1.STRICT tables provide a prescriptive style of data type management, for
developers who prefer that kind of thing.
2.When adding columns that contain a CHECK constraint or a generated column
containing a NOT NULL constraint, the ALTER TABLE ADD COLUMN now checks new
constraints against preexisting rows in the database and will only proceed if
no constraints are violated.
3.Added the PRAGMA table_list statement.
4.CLI enhancements:
a.Add the .connection command, allowing the CLI to keep multiple database
connections open at the same time.
b.Add the --safe command-line option that disables dot-commands and SQL
statements that might cause side-effects that extend beyond the single
database file named on the command-line.
c.Performance improvements when reading SQL statements that span many lines.
5.Added the sqlite3_autovacuum_pages() interface.
6.The sqlite3_deserialize() does not and has never worked for the TEMP database.
That limitation is now noted in the documentation.
7.The query planner now omits ORDER BY clauses on subqueries and views if
removing those clauses does not change the semantics of the query.
8.The generate_series table-valued function extension is modified so that the
first parameter ("START") is now required. This is done as a way to
demonstrate how to write table-valued functions with required parameters.
The legacy behavior is available using the -DZERO_ARGUMENT_GENERATE_SERIES
compile-time option.
9.Added new sqlite3_changes64() and sqlite3_total_changes64() interfaces.
10.Added the SQLITE_OPEN_EXRESCODE flag option to sqlite3_open_v2().
11.Use less memory to hold the database schema.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 29 Nov 2021 14:59:49 +0000 (22:59 +0800)]
libexif: upgrade 0.6.23 -> 0.6.24
libexif-0.6.24 Changelog:
Translation updates: sr, vi, pl, uk, french
fixed regression in exif_data_load_data which could not load EXIF in JPEG data anymore
Decode lots of Canon tag names
removed empty strings from translation (empty string would translate to the PO info header)
various warning removals and code improvements
added sample "persistent" afl fuzzer (100x faster than normal afl fuzzer)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 29 Nov 2021 14:59:51 +0000 (22:59 +0800)]
libunwind: upgrade 1.5.0 -> 1.6.0
0001-Add-AO_REQUIRE_CAS-to-fix-build-on-ARM-v6.patch
0001-configure-Do-not-enforce-libdir-for-ppc64.patch
removed since they're included in 1.6.0
refresh the following patches:
0003-x86-Stub-out-x86_local_resume.patch
0005-ppc32-Consider-ucontext-mismatches-between-glibc-and.patch
0006-Fix-for-X32.patch
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was additionally verified with meta-virtualization:
$ bitbake packagegroup-container packagegroup-kubernetes
$ bitbake container-base kvm-image-minimal xen-guest-image-minimal
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
testimage.bbclass: request the use of kvm by default
In almost all cases there is no need to explicitly ask for it via local.conf
or similar custom config:
it is enabled in qemu_use_kvm() if target_arch == build_arch or both of them are x86 archs,
and QEMU_USE_KVM is set.
If that heuristic doesn't work, QEMU_USE_KVM = "" will do the disabling.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj [Sat, 27 Nov 2021 09:22:39 +0000 (01:22 -0800)]
weston-init: Pass --continue-without-input when launching weston
This ensures that we do not need keyboard/mouse or other input system
Weston's default behavior is to not open if input devices are not
found, but we may not always have input devices connected for systems
running weston in field
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Jacob Kroon [Wed, 24 Nov 2021 05:31:10 +0000 (06:31 +0100)]
native/cross: Add ar wrapper for determinism
Add a wrapper around ar calls for native/cross recipes. This wrapper adds
the -D option so that deterministic archives are built for native/cross
output. This improves the changes of hash equivalence matches and hence
build artefact reuse.
We don't need this in the target case since we compile binutils-cross
with an option making this the default. We need a wrapper since we need
to remove the "u" option and replace it with "D" but also allow things like
"--version" to continue to work too.
Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 22 Nov 2021 16:11:45 +0000 (16:11 +0000)]
nativesdk: Handle chown/chgrp calls in nativesdk do_install tasks
We disable the useradd code for nativesdk targets since we don't support
postinstalls or multiple users in those cases. This means any usage
of chown/chgrp inside do_install tasks won't work and would have to be
conditional. Rather than require all recipes to do that, add intercepts
of the calls and map those to root/root user/groups. We can't just ignore
them as some calls are used to remove host contamination from the host
user ID so they need to be made, just as root.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Max Krummenacher [Mon, 22 Nov 2021 16:34:58 +0000 (17:34 +0100)]
perf: sort-pmuevents: don't drop elements
If a struct element neither has an element cpuid or name it gets silenty
dropped.
Kernel 5.15 for some ARCHs have at least one array of structs matching
this.
e.g. for arm pmu-events.c:
Bruce Ashfield [Tue, 23 Nov 2021 21:23:43 +0000 (16:23 -0500)]
kernel: introduce python3-dtschema-wrapper
The 5.16 kernel introduced mandatory schema checking on any dtb file
built through the kernel.
That funcionality is provided via python3-dt-schema.
The dependencies to enable that functionality is not small, and may
not always be desired (in particular on architectures that do not
support dtbs, or in development cycles). It may also be useful for
allowing a non-conformant dts to be compiled.
This commit introduces a set of wrapper scripts that when added
as a depenency to the kernel, can pass both the validation testing
and validation steps of a dts.
We use the wrapper by default, while more dts file are brought up
to spec and the dt-validation matures upstream.
To enable valiation, simply add 'dt-valiation' to the PACKAGECONFIG
variable and the full dt-schema package will be selected and
validation will occur.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 04:15:16 +0000 (23:15 -0500)]
linux-yocto: export pkgconfig variables to devshell
Not all of the kernel host/build Makefiles allow pkg-config
to be overriden to pkg-config-native. Exporting these variables
allow us to debug host tool issues with the kernel build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 03:54:28 +0000 (22:54 -0500)]
python: import rfc3339-validator from meta-python
Importing rfc3339-validator from meta-python, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 03:54:28 +0000 (22:54 -0500)]
python: import idna from meta-python
Importing idna from meta-python, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Thu, 25 Nov 2021 16:20:37 +0000 (11:20 -0500)]
python3-jsonpointer: Update 2.1 to 2.2
The import from meta-python was slightly out of date, and the
2.1 version was grabbed. We bump the oe-core version to 2.2
to match the latest meta-oe version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 23 Nov 2021 04:22:55 +0000 (23:22 -0500)]
kernel: export native PKGCONFIG variables
In a similar manner to cml1.bbclass, we export the pkg-config
variables to allow a direct call to pkg-config access to the
native sysroot versus the target sysroot.
The kernel doesn't use pkg-config for target configuration,
and has many explicit calls to pkg-config, without the
possibility of easy override to pkg-config-native.
The calls to pkg-config could be made cross friendly via
replacement with make variables, but until that effort is
undertaken upstream, we need a bridge approach.
In particular, this is required for dtschema validation,
which is a requirement in kernel 5.16+
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 04:17:09 +0000 (23:17 -0500)]
linux-yocto-dev: bump to v5.16+
Bumping the version of -dev ot 5.16. We also pickup two new
dependencies to support kernel dtschema validation. This
requirement was introduced by kernel commit:
It is possible to build a single dtb, but not with DT schema validation
enabled. Enable the schema validation to run for %.dtb and %.dtbo
targets. Anyone building a dtb for a specific platform *should* pay
attention to schema warnings.
This could be supported with a separate %.dt.yaml target instead.
However, the .dt.yaml format is considered an intermediate format and
could possibly go away at some point if schema checking is integrated
into dtc. Also, the plan is to enable the schema checks by default once
platforms are free of warnings, and this is a move in that direction.
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Cc: Tom Rini <trini@konsulko.com> Cc: Masahiro Yamada <masahiroy@kernel.org> Cc: linux-kbuild@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org> Acked-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.kernel.org/r/20210913145146.766080-1-robh@kernel.org Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Ross Burton [Wed, 24 Nov 2021 17:15:29 +0000 (17:15 +0000)]
oe/utils: by default cap cpu_count() to 64 cores
Larger systems may have large numbers of cores, but beyond a certain
point they can't all be used for compiling: whilst purely
compute-intensive jobs can be parallelised to hundreds of cores,
operations such as compressing (needs lots of RAM) or compiling (lots of
I/O) don't scale linearly.
For example, the Marvel ThunderX2 has 32 cores, each capable of
executing four threads, and can be configured with two sockets, making
256 CPUs according to Linux. Zstd using 256 threads has been seen to
fail to allocate memory during even small recipes such as iso-codes.
Add a default cap of 64 CPUs to the cpu_count() method so that extreme
parallisation is limited. 64 is high enough that meaningful gains
beyond it are unlikely, but high enough that most systems won't be
effected.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
