This updates the QEMU sounds options for x86 emulation,
when "runqemu" is called with the "audio" argument,
to fix the below error:
runqemu - ERROR - Failed to run qemu: qemu-system-x86_64: warning: '-soundhw ac97' is deprecated, please use '-device AC97' instead
(From OE-Core rev: b802a5dd1a79c7be3bc790223a733ebc9be4f117)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop libstd-rs patches as they're merged upstream.
(From OE-Core rev: 05f4a09899aa8dbb22ef1adb494abac41d5b96b7)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The only thing which needs perlcross-native will depend upon it directly
so we can optimise this out everywhere else for small space/speed gains.
(From OE-Core rev: 3b86109a2571be39f9cfa85bd4db22f4df025ab2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently, libarchive-native pulls e2fsprogs and all it's dependencies into
the sysroot. Since only headers are needed at buildtime and there is no
runtime dependency, we can avoid this and shrink the native sysroots.
(From OE-Core rev: 66a6b2080e4a65632c5dc02c8ef0cbe01d5b5082)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Where a recipe has depends on native docs tools, in most cases
we don't need recipes that depend on that recipe to also install
these things into the sysroot. We can rely on recipes wanting these
tools to have direct dependencies instead.
This massively reduced dependency creep in simple recipes (e.g. an
allarch one) and reduced the size of builds with the api-documentation
feature substancially.
gperf-native is also included since that would normally have a direct
dependency in a recipe which needs it too.
(From OE-Core rev: 9bbb5334e1d1884e042dc3b3ec0eb274664f2c25)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This re-writes the INCOMPATIBLE_LICENSE checking code to replace
the WHITELIST_<lic> with
INCOMPATIBLE_LICENSE_EXCEPTIONS = '<pkg>:<lic> <pkg>:<lic> ...'
This initial change leaves most of the code structure in place,
but the code in base.bbclass needs to be re-written to make
the check more consistent around packages (PKGS) and not recipe
names (PN). This also is taking into account the changes for SPDX
licenses.
The aim is to provide a mode consistent variable where the variable
name is known and can easily be queried.
(From OE-Core rev: 0d19c45ba6cf43518f380ca5afe9753a2eda0691)
Signed-off-by: Saul Wold <saul.wold@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In commit ceda3238 (meta/meta-selftest/meta-skeleton: Update LICENSE
variable to use SPDX license identifiers) all LICENSE variables were
updated to only use SPDX license identifiers.
This does the same for comments and other variables where it is
appropriate to use the official SPDX license identifiers. There are
still references to, e.g., "GPLv3", but they are then typically in
descriptive text where they refer to the license in a generic sense.
(From OE-Core rev: 165759dced7fbe73b1db2ede67047896071dc6d0)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is no reason to set an empty default for it, while not doing it
for all other potential WHITELIST_* variables. The reason it was set
here is a leftover from before when it was actually set to a value.
(From OE-Core rev: 22ccd479147744fcbf4f2e765e54da8d3d3d9c7f)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The code has not been touched since 2016 and numerous files still have
Python2 syntax code in them. This causes do_compile errors when
packaging a wheel (PEP-517 packaging).
Nothing in oe-core depends on python3-nose.
[YOCTO #14638]
(From OE-Core rev: 19135f8b7cbaabeb2e38572d11e909ce386d60b8)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The native recipe simply calls create_wrapper to add a host script. Do
this via do_install:append:class-native()
The scons*.1 man pages are being installed in ${prefix}, move them to
${mandir} (previously installed in ${datadir}).
[YOCTO #14638]
Drop from maintainers.inc
(From OE-Core rev: f91009d168bcad5df6b3ca4f5cd4babff5cf682c)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the core of one of the "new build system" tools--hosted
officially as part of the pypa (Python Packaging Authority)
repositories--it is an increasingly common build tool (e.g.
typing_extensions and tomli) as declared in pyproject.toml for
said packages.
This package provides a very simple bootstrapping method that builds
the source tarball (build_sdist) and a wheel (build_wheel).
Bootstrap -native by simply unzipping the wheel to
PYTHON_SITEPACKAGES_DIR.
Use pip to install the wheel for class-target.
Wheels are the official vehicle for delivering Python packages now.
Eggs (egg-info) are deprecated and will increasingly go away.
[YOCTO #14638]
(From OE-Core rev: 18717181e4a893fd7c309eb75443a868ec4e83eb)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is one of the "new build tools" which are part of pypa (Python
Packaging Authority) toolchain.
Wheels are the official delivery mechanism for Python packages, replacing
the now deprecated Eggs (egg-info).
[YOCTO #14638]
(From OE-Core rev: 78a4bccfa38c2d3a6a4a097319eec28c2bc357a7)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add entries for the removed variables TUNEABI_WHITELIST and INHERIT_BLACKLIST.
(From OE-Core rev: b3bf2862e221af157f545a216b56b9b393dcc66d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The SYSTEM and USER seperation between variables seems odd and not necessary,
drop it. Avoid the use of whitelist/blacklist and also change "packages" to
"recipes" since that misuse causes confusion.
(From OE-Core rev: 0df0eb6401a02139b9110bc95e21d97a67125ec5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the old class and rename VarFlag to SKIP_RECIPE, handling this
in base.bbclass for efficiency. This means a separate inherit is no longer
needed.
This change better describes what the VarFlag is doing since it
is implemeted with the SkipRecipe() function.
By moving this into base.bbclass we simplify the distro inherit.
(From OE-Core rev: a5f735746cba6af41a25aa2aa121453a8bc363b4)
Signed-off-by: Saul Wold <saul.wold@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After other variables were renamed in bitbake, update OE-Core to match.
(From OE-Core rev: 91812ba5a34598e03ad860745707c7cba1ae5d91)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After the change to bitbake, update the references in OE-Core to match the updates.
(From OE-Core rev: 193affb9f28b0116c3fd619834f145326fee08c5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the layers to use the kirkstone namespace. No compatibility is made
for honister due to the variable renaming.
(From OE-Core rev: 4a180aa5b30cc0906072d5b1e970eea41f1ce642)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We require the code to handle variable renaming which is in this version
of bitbake.
(From OE-Core rev: e0f5938737727c3a2d738cd595a1f891c444c3c8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rename the image, the test controller class/code/module and the underlying
image sentinel file to all match the controller terminology.
(From OE-Core rev: f87b32833ac5327c4659ab8c06af34e7bda83f83)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
example.com is proving unreliable at present so switch to our own connectivity
page instead. That page is very simple avoiding app overhead on our web server
which was an original reason for switching to example.com.
(From OE-Core rev: dc6b043cb75c5751b5a98afd2201aa31f9b4b9f6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this, the string "${PACKAGE_EXTRA_ARCHS:tune-armv8-crc}" will
show up in some bash tasks (notably opkg-arch-config.do_compile which is
how I found out about this) which will break things (besides obviously
not doing the intended thing of expanding to a list of architectures)
(From OE-Core rev: c5142f867aaa3fb6fc134781e2e54ce10eabd530)
Signed-off-by: Luna Gräfje <luna.graefje@orbitalsystems.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Package /usr/bin/ld.so in a separate package
ld.so is a new tool which is added as a symlink to original dynamic
linker so make it available with same name across architectures which is
useful to leveral features like --preload, --audit, and --list-diagnostics
more accessible to end users
(From OE-Core rev: 2658dcbcfc3db814af1ee104303effc1b6cfa489)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed to run weston properly as non-root in the absence
of systemd-logind, and other compositors will likely require seatd
as well.
(From OE-Core rev: f0c7e8cdeea065ddfcd4187f1fabc074b2753ba1)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Prelink is being dropped by glibc in 2.36. It already causes issues with
binary corruption, has a number of open bugs and is of questionable benefit
without disabling load address randomization and PIE executables.
We disabled it by default a while back but left people able to use it.
We would be unable to maintain it alone without glibc support so remove
the remaining pieces.
(From OE-Core rev: 23c0be78106f1d1e2bb9c724174a1bb8c56c2469)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the hash equivalence fix, we need to bump the sstate and hash equivalence
version numbers to ensure older task hashes aren't matched into the new namespace.
(From OE-Core rev: 3f229267e0588c747265e849ee19724033cc6a80)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping our reference headers to 5.16 to support newer kernels (-dev
in particular).
No issues were found in glibc or musl, and no patch referesh/drops
are required
(From OE-Core rev: a6a814fd1f62cc8050a438efb878a01aa3df7ae5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows automated version updates when possible, and reduces friction in manual ones.
(From OE-Core rev: 54d4a767ab7beaa64cfc4c221317ea03b0b119ab)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After the changes to the native outhash files to ensure populate_sysroot for
native recipes correctly accounts for runtime dependencies, this doesn't reset
the target output namespace and means reproducibility issues are still triggering
on our test infrastructure.
Bump the version being used for hashequiv to ensure we avoid these issues with
a new namespace.
(From OE-Core rev: 3510caa7245d1993b2dc54c7bf2c7a884dd10c88)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The crypto extension is optional for the Cortex-A73 processor, so we
shouldn't enable the crypto by default for the cortexa73 tune.
Introduce the cortexa73-crypto for the processors which do have
the cryptography unit.
(From OE-Core rev: c16b31ebd626d8a314264605d0bc5ab008cddd8d)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These were added nearly a decade ago but there are no users in OE-Core. I
checked with the likely users and they seem to have no current usage either.
Therefore remove them.
If needed for some prebuilt library somewhere, they could be implemented
in the layer using them instead but I doubt these are in use any longer.
(From OE-Core rev: 95e196babc3c18dcf0aedfb03e85493c8ae54700)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We have enabled the crc extension by default for cortexa72 in patch
("tune-cortexa72: Enable the crc extension by default for cortexa72"),
then the cortexa72-crc seems redundant. So drop it. We also rename the
cortexa72-crc-crypto to cortexa72-crypto. With these changes, it will
break the BSPs which used these two tunes, but it should be easy to fix.
(From OE-Core rev: 03cebdd7ef923a8ac5c8b7c12c7cefe7ca0158db)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds the support for the Neoverse N2 core, even though the
Neoverse N2 core implements the Arm v9.0-A architecture, but the support
of it in GCC is based on the Arm v8.5-A architecture. Please see the
commit 50d9db203bc3 ("aarch64: Add support for Neoverse N2 CPU") in GCC
for more detail.
(From OE-Core rev: 37597397f03b6b0082a702147dc536ff8b2fa7a3)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds support for the armv8.5a architecture and the crypto
extension.
(From OE-Core rev: 0cb1a6d9cb4c32526d79dad93c8053b3793053f8)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The crc extension is optional for the ARMv8.0 but is mandatory for the
cortexa72, so there is no reason not to enable it for the cortexa72
tune. With this change, the cortexa72-crc seems redundant. But we
had better to keep it to be compatible with the BSP which already used
that tune.
(From OE-Core rev: ca50267ab568d2f688844cb7c6cd867ed34168db)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.14 has been removed from the active kernel list, so we make
5.15 the new default.
(From OE-Core rev: 24fb6a22332f746e3bef89ff8e5719838f0ed8b5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
SDK recipes now require a provider for /bin/sh, this
should come from nativesdk-sdk-provides-dummy which
is added by default to Linux SDKs, however tclibc-baremetal
requires us to explicitly add its new dependency to
TOOLCHAIN_HOST_TASK, otherwise we get a packaging error
while generating an SDK.
e.g.
package packagegroup-cross-canadian-qemuriscv32-1.0-r0.x86_64_nativesdk
requires gdb-cross-canadian-riscv32, but none of the providers
can be installed
- conflicting requests
- nothing provides /bin/sh needed by
gdb-cross-canadian-riscv32-11.1-r0.x86_64_nativesdk
(From OE-Core rev: 8acb88cfe56735530280bab53a871c236f2fd54f)
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
SDK recipe now require a provider for /bin/sh, this
should come from nativesdk-sdk-provides-dummy which
is added by default to Linux SDKs, however tclibc-newlib
requires us to explicitly add its new dependency to
TOOLCHAIN_HOST_TASK, otherwise we get a packaging error
while generating an SDK.
e.g.
package packagegroup-cross-canadian-qemuriscv32-1.0-r0.x86_64_nativesdk
requires gdb-cross-canadian-riscv32, but none of the providers
can be installed
- conflicting requests
- nothing provides /bin/sh needed by
gdb-cross-canadian-riscv32-11.1-r0.x86_64_nativesdk
(From OE-Core rev: 9efcde387b31335d16394ce6b30e4abb1525185f)
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
