Include an upstream patch for 0.4.4 which fixes a test framework error
that occurs on host systems with symlinked /tmp directories (like OE).
(From OE-Core rev: 8064abb6664e16c6e0c63df3a466661f9b5b0d10)
Signed-off-by: Alex Stewart <alex.stewart@ni.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This backports a fix from glibc's master branch, which solves a
regression in 2.32 with adjtime() where it would seg fault if being
called with delta == NULL on 32 bit machines.
(From OE-Core rev: aeecccf17c45c840c070e2de95c602a3c7e9d30e)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new test to verify signing FIT images. Also includes testing for
the newly introduced FIT_SIGN_INDIVIDUAL, UBOOT_MKIMAGE,
UBOOT_MKIMAGE_SIGN, and UBOOT_MKIMAGE_SIGN_ARGS variables.
(From OE-Core rev: 3c054762278fd8c5dd827dbac15f4fa066e6c19e)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add verification of FIT_DESC to the existing test for kernel-fitimage.
(From OE-Core rev: 1d75a67efe968f1d9161b64e2b7b2d3cf482c968)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I'm about to add an additional test, and on the assumption that we might
also add more in future it seems reasonable to have the tests in their own
module.
(From OE-Core rev: 89f620cc142df9b4af6d49a13db96452ec838139)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add the ability to have the kernel, dtb and ramdisk individually signed
by setting FIT_SIGN_INDIVIDUAL = "1". This could be useful if you are
intending to verify signatures before using kexec for example.
(From OE-Core rev: 51b6e87df6babf74e73a6d704f044bd88c277ac9)
Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a UBOOT_MKIMAGE_SIGN_ARGS variable to enable passing additional
options to uboot-mkimage when it is run the second time to perform
signing.
(From OE-Core rev: 8fd7ee7414b45a1feeef7982af3583475902a677)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a UBOOT_MKIMAGE and UBOOT_MKIMAGE_SIGN variables to allow specifying
an alternative uboot-mkimage executable (or wrapper script/function).
(From OE-Core rev: aee5bac02eff28a75fa1eee646bc511984013aa4)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fitimage_emit_section_config() has a number of arguments, add named
variables to make the function a bit more readable.
(From OE-Core rev: a82340eed3165825c129c1f2b1ebf250e0e699c2)
Signed-off-by: Easwar Hariharan <eahariha@microsoft.com>
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a FIT_DESC variable to make it possible to change how the
description is set in the FIT image.
(From OE-Core rev: 47c5ea69e1a6c4fd3aa766d5223aff1201a4a1d8)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream is moving from Autotools to Meson, Autotools support will be
dropped in 15.0.
I dropped some configure options:
* --enable-tcpwrap=no doesn't (currently) have a counterpart in Meson,
TCP Wrappers support is always disabled.
* --disable-esound doesn't have a counterpart in Meson, EsounD support
is always disabled.
* --disable-gconf doesn't have a counterpart in Meson, GConf support is
always disabled.
I backported a patch that implements support for the -Dvalgrind=disabled
option.
I checked with buildhistory what the differences are before and after
this patch (with qemuarm with neon removed from TUNE_FEATURES, all
PACKAGECONFIGs enabled):
* Obvious differences in DEPENDS: Autotools stuff removed and Meson
stuff added. There wasn't anything strange here.
* Packages have superfluous RDEPENDS removed from them. With Autotools
something caused for example X11 libraries to be added to RDEPENDS of
packages that don't have anything to do with X11.
* The pulseaudio-src package had MMX and SSE related files removed and
Neon related files added. I don't know why the ARM build previously
had MMX and SSE files included, the addition of Neon files is
explained by the fact that with Meson the Neon optimizations can't be
disabled if the compiler supports Neon (see below).
* libfoo.so symlinks changed to point to libfoo.so.X rather than
directly to libfoo.so.X.Y.Z. To my understading that's fine, since
libfoo.so.X is a symlink that points to libfoo.so.X.Y.Z.
* There were various file size changes, which I didn't investigate.
Previously the recipe disabled ARM Neon optimizations when "neon" was
not in TUNE_FEATURES. That was originally added in commit
4e7b91b5a2613b957b08aefbee1aac28fdd19598 at a time when PulseAudio's
build system didn't check the availability of the arm_neon.h header,
causing compilation errors when the header wasn't available. That issue
was fixed a long time ago, so there was little need for the
TUNE_FEATURES check, although it was still possible to make the build
fail if non-neon -mfpu was passed in CFLAGS, so the TUNE_FEATURES check
still had some theoretical benefit (theoretical, because generally OE
passes -mfpu in CC instead of CFLAGS, so OE's -mfpu option appears very
early in the compiler command line, which doesn't trip up PulseAudio's
current Autotools build system).
With Meson there's no option for disabling Neon optimizations if the
compiler supports Neon. If -mfpu is set in CC or CFLAGS, it's ignored,
because the build system adds -mfpu=neon at the end of the compiler
command line, overriding any earlier -mfpu options. This shouldn't be
a problem, because PulseAudio detects at runtime whether the CPU
supports Neon instructions.
(From OE-Core rev: 80bbea06e706fde3600950ea9ddfc38a1a76b8bb)
Signed-off-by: Tanu Kaskinen <tanuk@iki.fi>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The GConf module is only needed for older versions of paprefs, other
applications shouldn't be interacting with PulseAudio's GConf settings.
Paprefs isn't packaged in OpenEmbedded, so there probably aren't any
users of the GConf functionality.
My immediate motivation for doing this is that I'm converting the
pulseaudio recipe to use Meson, and the GConf module isn't supported by
the Meson build system. Adding support for it would be possible, but
pretty pointless.
The GConf module will be removed in PulseAudio 15.0.
(From OE-Core rev: 6e06eb987002031c43f76f908caef240b556e6a1)
Signed-off-by: Tanu Kaskinen <tanuk@iki.fi>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This disables PulseAudio's EsounD emulation and the EsounD sink module.
EsounD has been obsolete for a long time, and doesn't seem to be
packaged for OpenEmbedded, so probably there are no applications around
that would need PulseAudio's EsounD support.
(From OE-Core rev: ee107217d2deee13d90b737bfb459838f27a94d9)
Signed-off-by: Tanu Kaskinen <tanuk@iki.fi>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I don't know what these variables were supposed to do, but there doesn't
seem to be anything that would use these variables, so removing them
should be safe. The PulseAudio recipe is the only place where these
appear in the repository.
These lines were included already in the original PulseAudio recipe that
was added in commit d9a4c588ef in 2007,
and already at that time there didn't seem to be anything using these
variables.
(From OE-Core rev: 7a0b9209a366de7a2aed9b23a337b4ffdba61abe)
Signed-off-by: Tanu Kaskinen <tanuk@iki.fi>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This also effectively reverts commit b6d30c21b0:
bitbake.conf: Extend PSEUDO_IGNORE_PATHS to ${COREBASE}/meta
The contents of ${COREBASE}/meta were ignored as pyc files could be
generated for the contents of the lib subdirectory if python modules
were imported within a pseudo context. However this doesn't protect us
from pyc files being generated in the lib directories for other layers.
It's far better to tell python not to produce pyc files when running
under pseudo (by setting the PYTHONDONTWRITEBYTECODE variable) as this
will cover any location where pyc files could possibly be created. This
variable is set in FAKEROOTBASEENV so that it applies to the
bitbake-worker instance for fakeroot tasks, preventing pyc files from
being generated for imports in python tasks themselves.
Also add a test case to ensure that pyc files are not created in tasks
which are executed under pseudo.
(From OE-Core rev: 73d538f20743017a44cea4c20dbe09a0327cfc71)
Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use oe.path.canonicalize() to canonicalize the paths in
PSEUDO_IGNORE_PATHS before passing them to pseudo. This is needed since
pseudo will compare them to paths that are canonicalized.
(From OE-Core rev: 1f2a497daa09cf3459e27ad6e0e8513938b52c79)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oe.path.canonicalize() is used to canonicalize paths (i.e., remove
symbolic links and "..", and make them absolute). It takes a string
with paths separated by commas, and returns the canonicalized path in
the same format.
(From OE-Core rev: 282b19c0e27488ec119f00fb2542ffdc1af54e2a)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
None is a bad choice of return value for functions used in variables
(strings) as a failure results in concatination errors. Use a string
with a clear meaning that can be searched for instead.
(From OE-Core rev: c04f04e714ede5d3904058ec82459139ed5e42fa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The get_hash() function is used to decide if the base configuration has changed
and hence whether a reparse is required. The vardepvalue flag's value was not
expanded but it is often used in contexts like:
METADATA_REVISION = "${@base_detect_revision(d)}"
METADATA_REVISION[vardepvalue] = "${METADATA_REVISION}"
which in it's unexpanded form means reparsing doesn't happen when it should
as the data appears unchanged. Update get_hash to expand the values of
vardepvalue so reparsing works as expected. This avoids basehash mismatch
errors such as the one recently caused by using METADATA_REVISION in poky.conf's
DISTRO_VERSION variable. The issue there could be exposed by a recipe using
DISTRO_VERSION with the sequence:
bitbake os-release
<change the revision of the metadata with a dummy commit>
bitbake os-release -C install
which was caused because METADATA_REVISION changed but the metadata didn't reparse.
(Bitbake rev: 26ccf1575aef2d6e2d7717d3bd10b1ed0d5a777d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a package for libopcodes, since, like libbfd, it is needed by
perf. Without separate packages for these libraries, all of the
binutil tools get added as well.
(From OE-Core rev: 514b595bda487ff74ae16539d716628a1d0be8af)
Signed-off-by: Alan Perry <alanp@snowmoose.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng-modules doesn't currently build against the lastest 5.10-rc
versions.
Upstream lttng does have fixes for the issues, but hasn't done a
release that contains them yet. There are other patches on the
2.12.x branch, but I've skipped them for now as they aren't
necessary for 5.10 builds, and can be picked up with the next
full update.
We also bump the dev-upstream hash to make them easier to pickup
for those building from git.
(From OE-Core rev: 47201e98bb293d59c5d41986d066fd7614b914fa)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit(s):
375e7ee20260 Linux 5.4.78-rt44
c948a34d2755 Linux 5.4.77-rt43
8189406f8f2b Linux 5.4.74-rt42
0856261877e2 timers: Don't block on ->expiry_lock for TIMER_IRQSAFE
416edb155e5d ptrace: fix ptrace_unfreeze_traced() race with rt-lock
6bd85935ab11 mm/memcontrol: Disable preemption in __mod_memcg_lruvec_state()
57ada856a2a8 net: Properly annotate the try-lock for the seqlock
1c80ecf69d2d Linux 5.4.74-rt41
d4318c110dc6 Linux 5.4.70-rt40
bdfc6168388d Linux 5.4.69-rt39
b6e0ef250594 Linux 5.4.66-rt38
151876f794fc Linux 5.4.61-rt37
4bdac3f47b53 Linux 5.4.59-rt36
cf9b41798238 Linux 5.4.58-rt35
631b98ae597b Linux 5.4.55-rt34
77d701a69ebb Linux 5.4.54-rt33
130cf1b82691 rwsem: Provide down_read_non_owner() and up_read_non_owner() for -RT
6ab4141069fc net: phy: fixed_phy: Remove unused seqcount
291d163db65a Bluetooth: Acquire sk_lock.slock without disabling interrupts
4c9f5d78fed4 workqueue: Sync with upstream
(From OE-Core rev: dfae903dd2538d57cc75e3b8b731515deb7f5526)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ensures that busybox init can generate matching tty's in inittab as
system defines, secondly resepcts USE_VT for creating virtual ttys
(From OE-Core rev: 7dddda7a00108f9a61da4a869514a32b9f42d16a)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qemuriscv enables hvc0 along with ttyS0, however its not enabled in
/proc/consoles, getty tries to enable it in inittab and erroring out
Fixes below message with sysvinit
INIT: Id "hvc0" respawning too fast: disabled for 5 minutes
(From OE-Core rev: 8a6559f1561ca6b7719bb46fc446db46d8086ea3)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otherwise, valgrind significantly slows them down, and actually
even causes ptest timeouts on arm64.
(From OE-Core rev: 483ca253cc25f928759263f9f3f2b3699e82252b)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Because the name of CVE patch is wrong, cve-check-tool cannot get the correct CVE result. Rename the patch name.
(From OE-Core rev: 422f9af7d0f7de7a2e933154853e7a281f98ab93)
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently there's no easy way to override this part as it's hardcoded
into the EXTRA_OEMAKE var. This change makes it possible to manipulate
the list of subdirs in a more fine graned and future oriented manner.
(From OE-Core rev: 1ca2b21cb7d638f36860bd16a90c1fb8238d4552)
Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These both now work on arm64, so add them to the dependencies.
(From OE-Core rev: 6b350db4ef9eaff10ee274ff7d28d2e6761c532a)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd-boot works on 32-bit and 64-bit Arm targets (assuming the
firmware does EFI, obviously), so allow it to be built.
(From OE-Core rev: 3325992e66e8fbd80292beb4b0ffd50beca138d8)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also build and deploy the EFI stub. SYSTEMD_BOOT_EFI_ARCH can be dropped
as image-uefi.conf now sets EFI_ARCH.
Changes originally taken from meta-intel.
(From OE-Core rev: 00191504bd9321334a5c01b95179ed15b063f1b6)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Refactor EFI_BOOT_IMAGE so that the EFI name for the architecture
is exposed as EFI_ARCH, so that other recipes (such as bootloaders)
can reuse it.
(From OE-Core rev: d3bf2d0fbd50309d7cf8f066c258ba1ebdb05f47)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we're not building syslinux, then there's no point building
syslinux-native.
(From OE-Core rev: 152dbd05c099ce50701466336a9c9642c98e4fe0)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently the syslinux recipe set COMPATIBLE_HOST to 32/64-bit x86.
Whilst this makes sense for the target binaries as syslinux is
x86-specific, this also affects the native recipe which should be able
to be built on non-x86 build hosts (for example, arm64 build host,
qemux86 target).
syslinux itself has a somewhat fragile build system but with care it is
possible to build the installer for native/nativesdk, and the bootloader
for target.
(From OE-Core rev: 7273e131bfc7de83df9e90697e7983d54b713798)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream release notes:
'''
* 20.8 - 2020-12-11
- Revert back to setuptools for compatibility purposes for some Linux
distros (:issue:`363`)
- Do not insert an underscore in wheel tags when the interpreter version
number is more than 2 digits (:issue:`372`)
* 20.7 - 2020-11-28
- No unreleased changes.
* 20.6 - 2020-11-28
- Note:
This release was subsequently yanked, and these changes were included in
20.7.
- Fix flit configuration, to include LICENSE files (:issue:`357`)
- Make intel a recognized CPU architecture for the universal macOS
platform tag (:issue:`361`)
- Add some missing type hints to packaging.requirements (issue:350)
* 20.5 - 2020-11-27
- Officially support Python 3.9 (:issue:`343`)
- Deprecate the LegacyVersion and LegacySpecifier classes (:issue:`321`)
- Handle OSError on non-dynamic executables when attempting to resolve the
glibc version string.
"""
(From OE-Core rev: 7a074958be6e166e2de98bd39dc203f0d67a8d93)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When using coreutils nativesdk (e.g. with buildtools-tarball) for
running oe-core builds, a number of recipes/classes/etc. expect xattr
support. This requirement is also expressed by the existing
PACKAGECONFIG_class-native default including xattrs.
(From OE-Core rev: 80d7debffdeed165006b26dcb89cffafaaecca06)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default ncurses includes the values of LDFLAGS in its output
pkgconfig .pc files. This causes issues because OE includes options that
are specific to either the build host, or build configuration. These
options are not expected to be embedded in the pkgconfig output that is
installed.
Specifically this change resolves issues with uninative, where uninative
includes '-Wl,--dynamic-linker=' in LDFLAGS in order to force the
building and execution of native binaries against the dynamic linker
provided by uninative. This path is specific to TMPDIR at the time of
build, such that the installed files (and the associated sstate) have
this path. This prevents the sstate from being portable across build
directories/hosts.
(From OE-Core rev: ef960d14bd9cecb9a3b50994636fbd455f06104a)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
