These fetcher *DIR variables were dropped a while back, drop the docs
that reference them (thanks Robert Day).
(From OE-Core rev: 609fcfe1f1490e9d9c35e40a0606a3b6b86bd78c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The security flags were missing from the SDK toolchain
because they were added specifically to class-target.
Add them to class-cross-canadian as well (since the SDK environment
file is created from cross-canadian target flags).
(From OE-Core rev: cd46e8f890069a40d1e9048cfa0f378dec1dc5e9)
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Antoine Manache <a.manache@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the layer core name to the new release name.
(From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It was used only by nss.
(From OE-Core rev: baecda5b32b66d09dadccbcbe706c5ec0a270568)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rpm was the last user in OE-core.
(From OE-Core rev: 15aa3bdf798b0e45a20f877e203f3750b623754f)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qemuarm64 on aarch64 host errors out when using kvm
qemu-system-aarch64: PMU: KVM_SET_DEVICE_ATTR: Invalid argument
qemu-system-aarch64: failed to set irq for PMU
Aborted
machines with GICv3 that don’t support GICv2 guests you must have ‘-machine gic-version=3’ on the QEMU command line.
(From OE-Core rev: 17e93c6464184d137b9590f17bfa879ae79d0cfc)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Babeltrace 1 vs. Babeltrace 2
The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was released.
Babeltrace 2 is a complete rewrite of the library, Python bindings, and CLI. It
is plugin based and offers much more features and potential than Babeltrace 1.
Because Babeltrace 2 is still a young released project, some distributions still
provide packages for the Babeltrace 1 project. Both projects can coexist on the
same system as there are no common installed files.
(From OE-Core rev: be52889ba5e5a2cf02f50b3f3acee8ca72ec494d)
Signed-off-by: Anders Wallin <wallinux@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The number of threads used, and the amount of memory allowed
to be used, should not affect sstate signatures, as they
don't affect the outcome of the compression if xz operates
in multi-threaded mode [1].
Otherwise, it becomes impossible to re-use sstate from
automated builders on developer's machines (as the former
might execute bitbake with certain constraints different
compared to developer's machines).
This is in particular a problem with the opkg package writing
backend, as the OPKGBUILDCMD depends on XZ_DEFAULTS. Without
the vardepexclude, there is no re-use possible of the
package_write_ipk sstate.
Whitelist the maximum number of threads and the memory limit
given assumptions outlined in [2] below.
(From OE-Core rev: 7927d5f6eaab48578b23db9a4c38e2f87f011353)
Signed-off-by: André Draszik <git@andred.net>
[1] When starting out in multi-threaded mode, the output is always
deterministic, as even if xz scales down to single-threaded later,
the archives are still split into blocks and size information is
still added, thus keeping them compatible with multi-threaded mode.
Also, when starting out in multi-threaded mode, xz never scales
down the compression level to accomodate memory usage restrictions,
it just scales down the number of threads and errors out if it
can not accomodate the memory limit.
[2] Assumptions
* We only support multi-threaded mode (threads >= 2), builds
should not try to use xz in single-threaded mode
* The thread limit should be set via XZ_THREADS, not via
modifying XZ_DEFAULTS or XZ_OPTS, or any other way
* The thread limit should not be set to xz's magic value
zero (0), as that will lead to single-threaded mode on
single-core systems.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
xz archives can be non-deterministic / non-reproducible:
a) archives are created differently in single- vs
multi-threaded modes
b) xz will scale down the compression level so as to
be try to work within any memory limit given to
it when operating in single-threaded mode
This means that due to bitbake's default of using as many
threads as there are cores in the system, files compressed
with xz will be different if built on a multi-core system
compared to single-core systems. They will also potentially
be different if built on single-core systems with different
amounts of physical memory, due to bitbake's default of
limiting xz's memory consumption.
Force multi-threaded operation by default, even on single-core
systems, so as to ensure archives are created in the same
way in all cases.
(From OE-Core rev: d96aa8594c8d7531da34645cadbac4f7549d8ae6)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
glibc version has moved on to 2.31.x
(From OE-Core rev: ef681222a918030d726a79cf04111fb5d0b66355)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Allow sstate use in Tumbleweed and other distros as they update glibc.
(From OE-Core rev: ccb374c279b260b1fd3460f6bfd1567240816055)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For GUI automation purposes, strong motivation for accessibility (a11y)
via python3-dogtail and python3-pyatspi2, so taking over from Anuj.
(From OE-Core rev: fb0a7ab133434febc78ce4f4d00f1192935ad95e)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without the proper default tune in TUNE_FEATURES, certain variables
won't expand correctly. MACHINEOVERRIDES won't add cortexa72-cortexa53:
TUNE_CCARGS won't add -mtune=cortexa72.cortexa-53, generating the toolchain
incorrectly.
Adding missing 'cortexa72-cortexa53' to both
TUNE_FEATURES_tune-cortexa72-cortexa53 and
TUNE_FEATURES_tune-cortexa72-cortexa53-crypto
(From OE-Core rev: eee65bed5ee39051541a0a3f2a311396d6e7326c)
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These are added as dependencies by mime class, which could be inherited
along with allarch and dependencies silently go into target specific
recipes and which then can result in sstate hash signature mismatches
when the allarch recipes are reused for another arch
[YOCTO #13805]
(From OE-Core rev: 510015ac81df969f690d6c8661b00bebe73b7fca)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Only md5sum and sha256sum are currently provided by HOSTTOOLS. Trying
to use any other checksum conversion will result in a build failure.
Fix it by adding other supported checksum utilities to HOSTTOOLS.
(From OE-Core rev: 78155e5fcff9362049b576d20e31c3519c48485b)
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We've found we need a way to cause a change in signatures and move
to a new hash 'namespace' with hashequiv. This introduces a variable
which allows us to do this.
(From OE-Core rev: 1c2d5aeae2fa2dfc16bc60b6cf0b310f826337fd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sadly, meson makes it very difficult to install tests: the test
configuration is written into host-specific binary files, which
can't be transferred to the target. (unlike autotools where
at least everything happens via Makefiles which can be patched
and tweaked via sed and env vars)
So the configuration has to be entirely recreated in shell.
I managed this for wayland, but weston proved too difficult.
I had filed bugs asking upstream to make the tests installable:
https://gitlab.freedesktop.org/wayland/wayland/issues/146https://gitlab.freedesktop.org/wayland/weston/issues/368
(From OE-Core rev: 296ee10bb8491278f050fb9d55f42b0bcf663382)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are no users left in OE-core.
(From OE-Core rev: 2c5d140a8a2b794b36ed9535afc278cec2ef306f)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are two primary reasons for this:
1. mdadm test suite tends to work like this
do_action
sleep arbitrary_amount
check_result
This is unreliable, and arbitrary_amount may or may not be enough.
I have confirmed this by increasing the amount, and seeing more tests
pass than before.
2. The test suite aborts half way through because one of the mdadm binaries
segfaults. This indicates that upstream isn't actually running the suite
anymore, and in this situation we shouldn't be relying on it either.
(From OE-Core rev: e21021dc00ec76c76cc361e15bc83a89083c9e72)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Details of changelog [1]
Removing bfd/ld patch to enable PE targets, instead use
specific emulations via --enable-targets for x86_64
Re-arrange/forward-port patches and upgrade libctf configure to libtool 2.4 patch
rpaths are no longer emitted into elfedit/readelf therefore no need of
chrpath anymore
Instead of pre-generating configure scripts and house them in libtool
patch, generate them during configure. This also ensures that we do not
patch configure directly but rather the sources which generate it
Package newly added libctf library
[1] https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html
(From OE-Core rev: 82f7d5cfc2ab02f39b69c0f8697d660936422d4a)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Christopher Clark <christopher.clark6@baesystems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that the 5.4 recipes are available, we bump the default versions
to use them.
(From OE-Core rev: c250dbd2a68048f83837e7cbdfb53bc38623e4a2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
webkit nowadays requires a couple of supplementary libraries for this,
so bring them in (courtesy of meta-webkit[1], which will hopefully
adjust without a lot of trouble).
[1] https://github.com/Igalia/meta-webkit/
[RP: Add missing maintainers entries]
(From OE-Core rev: 85431fe5c16ce1aa0916e57e820ff69c5aa0612a)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adds a recipe that packages jQuery in a manner borrowed from debian. The
primary purpose is to make the diffoscope output from the autobuilder
easier to navigate.
(From OE-Core rev: 9fdfff92e5f6b56657802c06c698ef37a95fd449)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Corrections:
- environment
- accommodate
- conversion
- compatible
(From OE-Core rev: 9797d3b45b4e1b9d77f0f2ee299c17b48d8d3cf6)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I am not sure if this has ever worked, but uvesafb is a really
outdated (VBE from the 1990s), awkward (needs v86d) and limited
(no support for high resolutions) way to do it.
The specific reason 640x480-32 was introduced (ages ago) was
to force 32 bit mode with vmware driver, as 16bit had rendering issues.
The modern, supported option is video=... kernel parameter documented here:
https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDIDhttps://github.com/torvalds/linux/blob/master/Documentation/fb/modedb.rst
which can be passed directly to runqemu and doesn't require special
kernel modules.
Sato under X will continue to use 640x480 as that is hardcoded into
xorg.conf under qemu.
(From OE-Core rev: 1cf26f69fd89b43be24cd1232c43e5050b9d718a)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was added ages ago to enable GL passthrough with
vmware driver, and is no longer relevant, as std or virgl is used
instead nowadays.
Original commit:
commit 072545b111
Author: Richard Purdie <rpurdie@linux.intel.com>
Date: Wed Jan 21 17:40:51 2009 +0000
scripts/poky-qemu-internal: Add support for GL passthrough in qemux86 images
(From OE-Core rev: 857078ba8eda153f4a097683db551a7d310ecc01)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we now have an example recipe on meta-skeleton to
build baremetal applications using OpenEmbedded, a user
produced SDK should be able to run such application.
Include nativesdk-qemu on TOOLCHAIN_HOST_TASK so its
built inside the newlib based SDK.
(From OE-Core rev: 9521c66e0edb2b36c3d5c777ec7a7158b40452d4)
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we now have an example recipe on meta-skeleton to
build baremetal applications using OpenEmbedded, a user
produced SDK should be able to run such application.
Include nativesdk-qemu on TOOLCHAIN_HOST_TASK so its
built inside the baremetal based SDK.
(From OE-Core rev: 2c6a249f3e1ad9c160f59d2d0b38749c85e7ff3a)
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While we are upgrading let's refresh patches and remove the outdated
patches.
(From OE-Core rev: ca276b77904429a1ff3188d2373535a462afe266)
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffoscope is the universal diff tool, capable of comparing many
different formats.
(From OE-Core rev: c92cf366c301a98ff1546d80d6c3a138f952252a)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The python-magic module is used by diffoscope tool to make
build comparisons.
(From OE-Core rev: 64560fcbe7c9658fcca86010502d00998d88f418)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The libarchive python module is used by diffoscope tool to
make build comparisons.
(From OE-Core rev: 288becda36dcc9f5435ec00258c0d0594e0011c1)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
running ptests on qemuarm returns fails since it finds errors in kernel
logs like below
***********************
Central error: [ 4.338465] pci-host-generic 4010000000.pcie: ECAM ioremap failed
***********************
Since its a 32bit kernel 4010000000 address is truncated to 10000000 and ends up
in conflicts with VIRT_PCIE_MMIO, which ranges from 0x10000000 to 0x3efeffff
This is happening because the linux-yocto kernel is not compiled with
LPAE support, however, virt machine for qemuarm assumes that by default
Should LPAE be enabled by default in kernel config is a separate
question
(From OE-Core rev: 4486f4523f6671841ffa65ce2419b9e3e018ad76)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default, we won't copy and strip static libraries. However, this
functionality can be useful in some cases where people are doing
development on the target, and don't generally want the larger debug
capable static libraries. To enable the new functionality set:
PACKAGE_DEBUG_STATIC_SPLIT = '1'
Add a new function splitstaticdebuginfo. Thus function will copy the
unmodified static library into the specific debug directory location.
By keeping an unmodified version, it is possible for a user trying
to debug something to use -L /usr/lib/.debug-static and their existing
build commands to switch from stripped to full debug versions.
The PACKAGE_DEBUG_SPLIT_STYLE will select between two different
approaches, /usr/lib/debug-static or <path>/.debug-static.
Additionally you can now choose to strip static libraries to conserve
space. If either 'PACKAGE_DEBUG_STATIC_SPLIT' or 'PACKAGE_STRIP_STATIC'
is set to 1, the static library will be stripped. (This is not on by
default, as it could make diagnosing static library usage difficult in
some cases.)
Add to insane.bbclass a skip to the staticdev warning for the specific
-dbg package versions.
(From OE-Core rev: 17fa66c8199d73f0b59b2b3e609075933bf1e74b)
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
chkconfig is one of the options for virtual/update-alternatives,
however opkg-utils have been used as the default for a very long time,
while chkconfig isn't anymore tested in any way, and is stuck
at a very old version due to newer versions requiring selinux.
[YOCTO #11264]
(From OE-Core rev: 61efc1e287326f52810a439ccde996f45ef89733)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
