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)
(From OE-Core rev: 7bfd1d2faa30cec9876901de718278ea013cc281)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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
(From OE-Core rev: fb4a298594e1722ab57cd312e391e6f7c5597f8a)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes in libsoup from 2.74.1 to 2.74.2:
* Error when libsoup3 is already loaded before libsoup2
(From OE-Core rev: 0640eb72ef4db97fc07011d8398dbafbd3c8b119)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds a smoke check for whether the Go toolchain actually
produces working executables across a range of architectures.
(From OE-Core rev: 2819bb2cf22c6cfcaeaee79f0280097ec9cb9327)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adjust SRC_URI, github is only a mirror.
Adjust GO_IMPORT, as it does not match either github
or the official repo.
(From OE-Core rev: 2c0e20fca1491adfef4f79b0088664f587ade4fd)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: c2a2d475a976225e3a4eb687af6d2a62dca1d2bf)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Somewhere along the way the issue was fixed upstream.
(From OE-Core rev: 8a5e34ff78fc74bce16b7aae173f047fce88dee5)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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
(From OE-Core rev: 762a20b493cc219a46d9ac188fe4895a111ee7b4)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
distutils is going away and we have functionality in bitbake which can
handle these comparisions so switch to the bb.utils function.
(From OE-Core rev: fe624b520e6c75e16a8f394785ab0216341402f9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a parameter `striplevel` to the SRC_URI to strip NUMBER leading
components (levels) from file names on extraction.
For example, if the archive `archive.tar.gz` contains `some/file`,
the SRC_URI `https://.../archive.tar.gz;subdir=other;striplevel=1`
will extract `some/file` to `other/file`.
This is useful to extract archives to a specified directory instead of
the original root component of the archive. The feature is required for
the npm support. The npm package contents should reside in a subfolder
inside a npm archive (usually it is called package/). npm strips one
directory layer when installing the package.
(Bitbake rev: aa4926e5d9c92f33b4434e2da709ff0bf3049f5b)
Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The tar command and its arguments are repeated for many archive types in
the unpack function. Unify the common parts in a variable to prepare
further extension.
(Bitbake rev: a08e57c9eaec1d9740a96149bf4843e576da4e5c)
Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed when oe-core's path contians append/prepend/remove, e.g.:
/path/to/append_test/oe-core/
Initial a build in any build dirs:
$ bitbake -p
ERROR: Variable __anon_32__buildarea2_xhou_builds_append_test_layers_oe_core_meta_classes_patch_bbclass
contains an operation using the old override syntax. Please convert this
layer/metadata before attempting to use with a newer bitbake.
The anonymous fuctions has no names, so skip checking for it to fix the issue.
(Bitbake rev: ebd00330c41c75797529ff38d6a0955b93f05d1b)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
According to comments on the bug report from gcc developers, we
no longer need to do this post gcc 10. Lets therefore drop the patch.
(From OE-Core rev: 8ddc6f46d40cdcc462de23d1b1218f2ed9fd3d07)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 59922c95fcb20c66634c5677012d490be2246b0b)
Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gcc-configure-common.inc already sets --with-abi=64 for our mips64
targets so this patch is no longer needed.
[YOCTO #14639]
(From OE-Core rev: e0010af733825ed1050fd3342cf3ef1c478df1a0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: e1f40670c438e33cae87678425de72ca03566888)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With kernel 5.16 some structs in pmu-events do get a const qualifier, some
a static const storage class and qualifier.
The current sort-pmuevents cannot cope with that and drops all struct
arrays with such additional elements. This then leads to compiler errors.
Allow '^struct', '^const struct', '^static struct', '^static const struct'.
(From OE-Core rev: 8406e83ade1c34d8a7d8063f2e7445aafa471721)
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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:
|#include "pmu-events/pmu-events.h"
struct pmu_events_map pmu_events_map[] = {
{
.cpuid = 0,
.version = 0,
.type = 0,
.table = 0,
},
};
struct pmu_sys_events pmu_sys_event_tables[] = {
{
.table = 0
},
};
Before this patch the second struct is translated to an empty array::
struct pmu_sys_events pmu_sys_event_tables[] = {
};
(From OE-Core rev: e1382583cd5060be301afaa9998ccf250cc8bca3)
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a PACKAGECONFIG to control which type of dt-validation
is installed (full, or wrapped).
This is currently in linux-yocto-dev, as 5.16 introduces
the functionality of required dt schema validation.
Other v5.16 providing recipes can use the base functionality
as they desire (with or without PACKAGECONFIG).
Over time, we can migrate the support the the core
kernel classes .. in particular when more providers are at
v5.16+
(From OE-Core rev: c12a91827e88230b4ec702a88534d4c51c1aabe3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: a8525391f8a519426c92f0e28895f426bfcb3f84)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: ea71e50be2de5b7fc81f466ea5cd48c2f1e0ef6b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add missing HOMEPAGE entries to new python recipes from meta-python.
(From OE-Core rev: 333af4b995f62406898e7efcebd5e846cdc449f6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These packages are required for dtschema checking in the
kernel build. Adding myself as the maintainer.
(From OE-Core rev: dff7ce9b72d54a0af0916424738ca0295eebc6c0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
vcversioner is a dependency of jsonschema, which is being
imported to support kernel device tree validation.
(From OE-Core rev: 51265151041cf71f3bc799fc60662df6f2cfd7ae)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
strict-rfc3339 is a dependency of jsonschema, which is being
imported to support kernel device tree valiation.
(From OE-Core rev: 1f00aad201b207e991d7679fbf45e7a308f48dd0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rfc3987 is a depenency of jsonschema and dtschema, which are being
added to support kernel device tree validation.
(From OE-Core rev: 9a3cb1a02a4c630e98137edcc8e33bd00343a957)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pyrsistent is a dependency of python3-jsonschema, which is being
imported to support kernel device tree validation.
(From OE-Core rev: e25d4417bc4ca01474c74dc5bd38594bcfbe6639)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing ruamel-yaml from meta-python. This package is a
dependency of python3-dtschema, which is required to validate
kernel devicetrees.
(From OE-Core rev: 748f7d377b62a0cd6bae558791a4d84b8110ea1a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing webcolors, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
(From OE-Core rev: cbba71e821815f97bb1dcadadc067d28b9d1e5ab)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing rfc3986-validator, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
(From OE-Core rev: ffe53365633833e5134744730b00c74cbb462752)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 8f9ade9448c1c87004d81bec049136a745dfb0b1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing idna from meta-python, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
(From OE-Core rev: 14fdb80c3c32e728f32d798134acaef6250c001a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing this package as a dependency to python3-dt-schema,
which is required for kernel device tree validation.
(From OE-Core rev: c28fd66c673a852d287220ec0c9fe882464a0161)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
