Recipes are much more readable with whitespace around the assignment operators.
Fix various assignments in OE-Core to show this is definitely the preferred
formatting.
(From OE-Core rev: 30ea609d3357fb3de911f2f6a5e6856c151b976a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It was created in 2004 as an alternative to hdparm and never updated since
(while hdparm remains in active development).
(From OE-Core rev: 54c1243a259a2f6407c0202d03414fc5272b2d90)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to packagegroup-core-tools-profile run time depend
on package valgrind and recipe valgrind does not support
loongarch64, then skip VALGRIND for loongarch64
$ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf
$ bitbake world
|ERROR: Nothing RPROVIDES 'valgrind' (but oe-core/meta/recipes-core/
packagegroups/packagegroup-core-tools-profile.bb RDEPENDS on or
otherwise requires it)
|valgrind was skipped: incompatible with host loongarch64-wrs-linux
(not in COMPATIBLE_HOST)
|NOTE: Runtime target 'valgrind' is unbuildable, removing...
|Missing or unbuildable dependency chain was: ['valgrind']
|ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
|Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
'packagegroup-core-tools-profile', 'valgrind']
(From OE-Core rev: 2ef616b4e43f5c4d3155201f743e48d6ff6bb400)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to recipe packagegroup-core-tools-testapps run time depend
on package kexec and recipe kexec-tools does not support
loongarch64, then skip KEXECTOOLS for loongarch64
$ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf
$ bitbake world
|ERROR: Nothing RPROVIDES 'kexec' (but oe-core/meta/recipes-core/packagegroups/
packagegroup-core-tools-testapps.bb RDEPENDS on or otherwise requires it)
|kexec-tools RPROVIDES kexec but was skipped: incompatible with host
loongarch64-wrs-linux (not in COMPATIBLE_HOST)
|NOTE: Runtime target 'kexec' is unbuildable, removing...
|Missing or unbuildable dependency chain was: ['kexec']
|ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
|Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
'packagegroup-core-tools-testapps', 'kexec']
(From OE-Core rev: 37ff515da6e13126f8822b3a55e44cdc62882a51)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
VIRTUAL-RUNTIME_keymaps is defined in busybox init manager and also in
some package groups. Defining distro features in recipes is wrong.
Also this is not directly related to init manager.
So move all these definitions to default-providers.inc
(From OE-Core rev: 00f667bb5007a372950a137bf9e8b0e62f44f7d6)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently VIRTUAL-RUNTIME_dev_manager is defined by some init managers
with "??=" and in packagegroup-core-boot with "?=".
This means that this variable is different in this package group and in
all other the recipes.
This was discovered when trying to use new feature INIT_MANAGER when
migrating to scarthgap and using systemd distro. After deleting all
VIRTUAL_RUNTIME providers defined in init-manager-systemd udev was
installed additionally via packagegroup-core-boot.
Having a distro settings overriden in single recipe is wrong and needs
to be corrected. Therefore let's define the setting in all init managers
and remove it from packagegroup-core-boot.
core-image-tiny-initramfs has a dilemma - use busybox-mdev even if
distro does not enable it in busybox recipe to keep the image tiny, or
rather not install it even if distro enables it in busybox.
This patch chooses the first option.
(From OE-Core rev: 89e2652ac83f2602d6dd60623a225b88dc67d288)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
makedumpfile is not compatible with mipsarcho32 and riscv32, so set for
kexec-tools accordingly.
And update packagegroup-core-tools-testapps too.
(From OE-Core rev: 9107d9c09c7dab385c6034778cefadca3613be9c)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Valgrind recipe has had support for aarch64 for 9 years but the
packagegroup-core-tools-profile recipe still excludes valgrind on
aarch64 builds. This patch adds Valgrind when building the
package-group-core-tools-profile for aarch64 systems.
(From OE-Core rev: 2f8f6d722b39d2d1080367bf780dead4ed4ed781)
Signed-off-by: John Ripple <john.ripple@keysight.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the distro features sysvinit and pni-names are
enabled, RRECOMMENDS ifupdown because busybox ifupdown
will not initialize the renamed interfaces.
(From OE-Core rev: ad739fb930814bced49aafe778dac1da4bfa4b0e)
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that bitbake supports the use of inherit_defer, switch all conditional
(variable based) inherits to use this instead. This leads to more a more
deterministic user experience since there is no longer an immediate expansion
and later changes to the variables in question (e.g. a bbappend) are
accounted for.
This patch tries to ensure the behaviour before/after remains as unchanged
as it reasonably can, e.g. by always inherting populate_sdk_base. native
and nativesdk continue to need to be inherited last, hence being used
with inherit_defer in a handful of very specific cases.
(From OE-Core rev: 451363438d38bd4552d5bcec4a92332f5819a5d4)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since commit d085e70eee ("sysprof: move recipe to meta-oe")
PROFILE_TOOLS_X is always set to an empty string.
Remove PROFILE_TOOLS_X as it is no longer needed.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From OE-Core rev: cf767f4f4aaaf7c568816675c1c811132a892e30)
Signed-off-by: Fabio Estevam <festevam@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We've been removing PR values from recipes at upgrade time for a while. In general
anyone maintaining a binary distro would end up having to curate these themselves
so the values in OE-Core aren't really that useful anymore. In many ways it makes
sense to clear out the remaining ones (which are mostly for 'config' recipes that
are unlikely to increase in PV) and leave a clean slate for anyone implementing
a binary distro config.
References are left in meta-selftest since the tests there do involve them and
their removal upon upgrade.
(From OE-Core rev: d4c346e8ab8f3cae25d1b01c7331ed9f6d4f96ef)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
we now have more rust/cargo recipes and tests that cover various use cases
so this is no longer needed.
(From OE-Core rev: 8baaf94d200f5355791ecd980727698b1ab0e539)
Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
APM has been obsolete for a very long time, and debian no longer
packages it or carries the source tarball.
(From OE-Core rev: d987b79725eb0da2704091d22e3d16b8026fac7d)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add missing tools necessary on the host for a build.
(From OE-Core rev: 15ba0ced2e8d4c2f9d6889b9b84c5525bc451e3f)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several of the lists of packages are alphabetized, but the alphabetization
was lost in a couple areas.
(From OE-Core rev: 4965a14dd51242d4d5ecc4b5f288d0c42bafae18)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
No longer package go-runtime-staticdev into sdk packagegroup,
as go-runtime 1.20 doesn't build the static bits anymore
(possibly can be enabled via build config, if proven necessary).
(From OE-Core rev: e8ab9d303a6fca3806097f1fd360efe8f8ae0c1d)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
init-ifupdown provides an /etc/network/interfaces, which disables
interface management with networkmanager for example. If a network
manager (such as networkmanager) is provided, there may not be a need
for network related init scripts provided by init-ifupdown, so let's
make it a recommendation so it can be easily removed in image recipes
via the NO_RECOMMENDATIONS/BAD_RECOMMENDATIONS mechanism.
Cc: Quentin Schulz <foss+yocto@0leil.net>
(From OE-Core rev: 719d1b74bfa85af47e0478ee57fb7855988e44ae)
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use SDK_TOOLCHAIN_LANGS to allow different language support to be
selected within SDKs. Initially supported options are rust and go.
(From OE-Core rev: 1ad7bb050accd930c85b6c51721046867394f629)
Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building rust crates it is quite common to have a build script [1]
that is compiled for the host machine and then used during build for target.
Currently when adding packagegroup-rust-cross-canadian this does not work
without having the native compiler and linker added to the SDK.
Add those packages to the packagegroup to make it easier to handle.
The reason for having glibc-dev and libgcc-dev is to have version match
with the used tools. Otherwise it will work on hosts that have compatible
gcc and glibc versions but not on all.
[1] https://doc.rust-lang.org/cargo/reference/build-scripts.html
(From OE-Core rev: 1de29eb5ec091427560e1f0b6b16c91a3a994835)
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Possible options would be wpa-supplicant or iwd.
iwd is a wireless daemon written by intel and supported by all major network managers.
It can be run in standalone mode and configured with 'iwctl' from the terminal, and
with 'iwgtk' or 'iwdgui' from the gui. It can also work as a wpa_supplicant drop-in
replacement for network-manager, connman or systemd-networkd.
iwd makes heavy use of the kernel api, so it is not portable but does not need
additional external libraries like openssl.
The PACKAGECONFIG name for wpa-supplicant in the connman recipe is changed accordingly,
so that it also works there when WIRELESS_DAEMON is set globally.
(From OE-Core rev: c54f3847349173ed3a8e77a5c2732e1bbcddd540)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
strace has been set imcompatible with riscv32, so update in
packagegroup-self-hosted.bb accordingly.
(From OE-Core rev: d326c561f90666f292d55b029e358c86b765b7c4)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enable rust target builds as well as nativesdk-rust for the sdk. Merge
the builds of rust-tools components into the rust build, packaged separately
since this is a lot more efficient and saves rebuilding core rust multiple
times. The tools are not target specific so nativesdk-rust-tools suffices
and we can drop the cross canadian piece.
(From OE-Core rev: b9b0cd99cdc77e7a90e5fd5711e706ebe64c7b6b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The cargo-cross-candian variant made no sense as one version of cargo in
the SDK can work for all targets. Replace it with nativesdk-cargo instead.
Move the SDK env to rust-cross-canadian.
(From OE-Core rev: 6d6d135924eff5993736ee58ba8cc5d00ca635f3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Seems sad to have to do this but openssh is moving to use sftp instead
of scp to move files. This means scp from Fedora 36 will no longer be
able to move files to/from a dropbear based image. This breaks a number
of our key QA tests and I suspect will cause users pain too.
The sftp server from openssh is small (200kb uncompressed) and standalone
so adding it to the packagegroup seems to be the best way to preserve user
sanity. If people really don't want it, they can just use dropbear instead
of the packageground.
(From OE-Core rev: a98188e83b2c027d99cc38e3367e1ec2a98efbb0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lzo isn't needed to build, so it doesn't need to be in the self-hosted
packagegroup.
(From OE-Core rev: 28beab2c5c90b66269bda89b2c0bed21018a0a61)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds a smoke check for whether the rust toolchain actually
produces working executables across a range of architectures.
(From OE-Core rev: 14bb638b0df7acfa6aa89abf4625357f8cde886b)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
go-helloworld is not compatible with riscv32 and causes error:
| ERROR: Nothing RPROVIDES 'go-helloworld' (but
meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb
RDEPENDS on or otherwise requires it)
| go-helloworld was skipped: Unsupported CPU architecture: riscv32
Clear GOTOOLS for riscv32 in recipe packagegroup-core-tools-testapps.
(From OE-Core rev: 16a730c803baef51b9475fbb67ece2d2c494d140)
Signed-off-by: Kai Kang <kai.kang@windriver.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>
The libstdc++ dependency is debian renamed so this shouldn't be allarch,
mark accordingly.
(From OE-Core rev: ac6ec1979caa4032b710eb6f6523bcca29d42cd4)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The wayland-scanner host tool required to build weston is moved to the
wayland-tools package, so update the SDK host tools list accordingly.
Also, the weston build requires wayland-scanner.pc to find wayland-scanner,
so add wayland-dev.
(From OE-Core rev: 31ed91bdbb0ec05730fb98d7cc523bb46aca50e3)
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recipe can't be built for riscv32 so exclude it alongside riscv64.
(From OE-Core rev: 61feb650ac450db0a30675fc40bb65fab773159a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kernel commit 12dd461ebd19 ("crypto: arm64 - generate *.S by Perl at
build time instead of shipping them") uses perl to generate assembler
files for crypto functionality, which relies on the integer.pm module to
be provided.
Add perl module to package group and export it in SDK.
(From OE-Core rev: 9f4c95a874f6a463b7d56bacea9ba321e29499f9)
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the result of automated script conversion:
scripts/contrib/convert-overrides.py <oe-core directory>
converting the metadata to use ":" as the override character instead of "_".
(From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is apparently no functional value to "PROVIDES" lines anymore in
packagegroup recipe files, so remove the lonely couple of examples
left.
(From OE-Core rev: 6f2c9602bc5fc6794b852ec20f40ea62a55ada1e)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The hdparm and (base) e2fsprogs are not always useful in all machines
having ext2 in MACHINE_FEATURES, so do not force them to b installed,
make them recommendations instead.
(From OE-Core rev: 17ec69be55a6b7572947704c07d8693d47d7f1d1)
Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Including alsamixer, which is an ncurses based interactive program,
does not seem to make sense as a base package in embedded systems,
replace it by the command line mixer utility amixer instead; it is
scriptable and has no ncurses dependencies.
(From OE-Core rev: 5e80b093a893600ed402701251fe0bdc9c10bb45)
Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The perf recipe builds fine for musl on ARM.
Fixes: d758a4445a ("packagegroup: Disable packages not available on musl")
(From OE-Core rev: 7a905f66d3a6d9018b18c1a8021c1cb8bf7d12ac)
Signed-off-by: Christian Eggers <ceggers@arri.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These tools are not yet ported to rv32/musl
(From OE-Core rev: cf963ef65d524256c2d00e0588cd3b8b7ef56ff4)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some platforms support kernel tracing, some support userspace tracing.
This change:
* Moves the knowledge/config to one place in an inc file
* Allows lttng-tools to build without lttng-modules
* Hence enables tools+ust for riscv64
* Has the packagegroup just depend on lttng-tools which will pull in
ust/modules as needed
(From OE-Core rev: 1824cf062df928de65c1bff5e86e26b7b4d9d784)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
