Not hardcoding the version of busybox from the core layer in this layer
is a small improvement for maintenance.
But the main motivation is to support the following layer combination
without getting a parse error from bitbake:
- poky LTS, branch = kirkstone
- meta-lts-mixins, branch = kirkstone/go
- meta-lts-mixins, branch = kirkstone/rust
- meta-virtualization, branch = master
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
OEcore has an update to busybox, and since we include the core
recipe directly, we have to update our PV to match.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
OE core commit a7d5150b621c2ab4e4 has bumped busybox to 1.35.0, so
we update our initrd recipe accordingly.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
OEcore/bitbake are moving to use the clearer ":" as an overrides
separator.
This is pass one of updating the meta-virt recipes to use that
syntax.
This has only been minimally build/runtime tested, more changes
will be required for missed overrides, or incorrect conversions
Note: A recent bitbake is required:
commit 75fad23fc06c008a03414a1fc288a8614c6af9ca
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Sun Jul 18 12:59:15 2021 +0100
bitbake: data_smart/parse: Allow ':' characters in variable/function names
It is becomming increasingly clear we need to find a way to show what
is/is not an override in our syntax. We need to do this in a way which
is clear to users, readable and in a way we can transition to.
The most effective way I've found to this is to use the ":" charater
to directly replace "_" where an override is being specified. This
includes "append", "prepend" and "remove" which are effectively special
override directives.
This patch simply adds the character to the parser so bitbake accepts
the value but maps it back to "_" internally so there is no behaviour
change.
This change is simple enough it could potentially be backported to older
version of bitbake meaning layers using the new syntax/markup could
work with older releases. Even if other no other changes are accepted
at this time and we don't backport, it does set us on a path where at
some point in future we could
require a more explict syntax.
I've tested this patch by converting oe-core/meta-yocto to the new
syntax for overrides (9000+ changes) and then seeing that builds
continue to work with this patch.
(Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
OE core has updated busybox, so we bump to match.
Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Add nsenter to Busybox configuration as it is required by Podman at runtime
Signed-off-by: Nathan Dunne <Nathan.Dunne@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
We already have a distro feature that controls the static/non-static
configuration of libgcrypt: 'vmsep'
To avoid build errors on distros that don't have static libgcrypt
available, we move the CONFIG_STATIC config to a fragment and only
enable it whent he distro feature is set.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Add a busybox variant that inherits almost all of its support from
the core busybox recipe, but adds configuration values that are
appropriate to be used in an initrd.
In particular:
- we build busybox statically
- we enable runlevel and init functionality
- mdev is always enabled
- applet install support is enabled
Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Runx needs busybox static binary that contains symlinks to mount. However, in
zeus, busybox by default uses BUSYBOX_SPLIT_SUID = 1. With the variable set,
busybox binary gets split into two busybox.suid and busybox.nosuid busybox.suid
contains links to mount while runx recipes pulls in busybox.nosuid.
When vmsep is enabled, set BUSYBOX_SPLIT_SUID = 0 so that an unstripped busybox
binary is generated which contains all the required links including mount.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
If "vmsep" is in distro features, we need to configure busybox
as a static build. This allows for it to be used as party of an
initrd.
We also ensure that the installer support is added to busybox, so
it can be installed to the initrd via: busybox --install
Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com>
This prevents the signature from being modified
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The commit "busybox: remove awk -F patch" missed the SRC_URI
update for the dropped patch.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The awk patch being carried by meta-virtualization is part of the
1.21.1 busybox release. So we can drop it from the bbappend.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Patch implements functionality mentioned in the title and has
been applied to busybox 1.21.0. This patch is included into the
meta-virtualization layer since it provides awk functionality to
the lxc-clone command in the lxc containers package.
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@freescale.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
