- Document the new KERNEL_DTBDEST and KERNEL_DTBVENDORED variables
- Also document the related KERNEL_DEVICETREE_BUNDLE
and KERNEL_PACKAGE_NAME variables
(From yocto-docs rev: 19f128e725da35234ec2c234c667ee7ff3d67d8d)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Mentioning that they are related to this class
(for further information about their usage)
- Replace "fitImage" by "FIT image"
- Minor formating and style fixes
(From yocto-docs rev: 07214a4ff2646efb143a02fc9381a029870e9b56)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
CC: Jamin Lin <jamin_lin@aspeedtech.com>
Reviewed-by: Sean Anderson <sean.anderson@seco.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Document the newly added DT_FILES variable and closely related
DT_FILES_PATH. Also add DT_PADDING_SIZE to the glossary.
(From yocto-docs rev: 8f3f187e2353c718c6fb4e224d13ba559ad2f85b)
Signed-off-by: Petr Kubizňák <kubiznak@2n.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Update the Mickledore starting and ending time
- Mickledore is no longer a future release
(From yocto-docs rev: 47b5eba8a38df4bfc6c704d3cfb7a24bfd8c4dce)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.15 doesn't work with gcc 13 and we'll be replacing 5.15 with a new kernel
version later in the release cycle. Drop 5.15 now so we can move forward
with gcc 13 and we'll add a new kernel version later.
(From meta-yocto rev: 084d840d7f655466d5d668ca309a8b09b83f23fb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gcc 13 appears to trigger TMPDIR changes in glib which causes ptest failures:
FAIL: glib/utils-c-90.test (Child process killed by signal 6)
FAIL: glib/utils.test (Child process killed by signal 6)
FAIL: glib/utils-c-99.test (Child process killed by signal 6)
FAIL: glib/utils-c-17.test (Child process killed by signal 6)
FAIL: glib/utils-c-11.test (Child process killed by signal 6)
The issue is caused by our symlinks between tmp directories which
cause the tests to get confused. We can set G_TEST_TMPDIR to
a resolved path using readlink to avoid the failures.
(From OE-Core rev: 7ef0ce88e23c7ca138bc4041931d9bfe1d85dfc0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a couple of patches from upstream which fix a failing test with gcc 13.
(From OE-Core rev: 9148de637f565578a96e8c02bad765ce3daffe27)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.15 doesn't work with gcc 13 and we'll be replacing 5.15 with a new kernel
version later in the release cycle. Drop 5.15 now so we can move forward
with gcc 13 and we'll add a new kernel version later.
(From OE-Core rev: e30b37776d16cfd4ce7f79746427ccd95b306059)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When the user configures the TMPDIR variable in a way that it contains $HOME (in local.conf), the DataSmart (d) object's PATH variable will also contain $HOME.
As the NpmEnvironment patches HOME with a temporary directory, further evaluation of PATH will become invalid an the build breaks with an error (npm not found).
As countermeasure PATH is evaluated *before* patching HOME.
(Bitbake rev: 893f3b116b628457fe0bfaf4b8394b1cd05a90a5)
Signed-off-by: Arno Baumfalk <a.baumfalk@astro-kom.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are times when it would be useful for code to know which layer
(or collection in old bitbake terms) it is contained within.
Add support for FILE_LAYERNAME to be set by bitbake when parsing a recipe
so that it is possible to determine this. To do it, we need to pass data
from the cooker into the recipe endpoints, since only the top level cooker
information knows about the layer structure which makes the patch a bit
painful.
The idea is that this would make layer overrides possible:
OVERRIDES .= ":layer-${FILE_LAYERNAME}"
which then opens possibilities like:
WARN_QA:append:layer-core = " patch-fuzz"
as an example where OE-Core could enable specific QA tests only for that
specific layer.
(Bitbake rev: 7090a14b0035842112d073acf7f2ed1a01fdeccf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It fails to instal pm-utils and lib32-pm-utils at same time:
Error: Transaction test error:
file /usr/bin/pm-is-supported conflicts between attempted installs of lib32-pm-utils-1.4.1-r1.corei7_32 and pm-utils-1.4.1-r1.corei7_64
file /usr/sbin/pm-hibernate conflicts between attempted installs of lib32-pm-utils-1.4.1-r1.corei7_32 and pm-utils-1.4.1-r1.corei7_64
file /usr/sbin/pm-powersave conflicts between attempted installs of lib32-pm-utils-1.4.1-r1.corei7_32 and pm-utils-1.4.1-r1.corei7_64
file /usr/sbin/pm-suspend conflicts between attempted installs of lib32-pm-utils-1.4.1-r1.corei7_32 and pm-utils-1.4.1-r1.corei7_64
file /usr/sbin/pm-suspend-hybrid conflicts between attempted installs of lib32-pm-utils-1.4.1-r1.corei7_32 and pm-utils-1.4.1-r1.corei7_64
All of the conflicted files either is script which source a file in
${libdir}, or a link file to some file in ${libdir}. Compare the content
of installed files in ${libdir} exclude binaries, only the paths of
${libdir} diff. So re-define libdir with ${nonarch_libdir} to fix the
conflicts.
(From OE-Core rev: f836541bcfdbf033a37537530b4e3b87b0a7f003)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch should have been dropped when upgrading to 253
since its already available upstream since then
(From OE-Core rev: 5b677b766280b39e8bf507d5aec4f08e49fd72a9)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was needed to use provide different llvm from meta-clang or other
layers, seems unused since meta-clang has stopped providing a versioned
llvm
(From OE-Core rev: 7012aefb10a4101b2f3baf4dc20c64e3260b4cc8)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you have a host where the git config for initial branch
name is something else than 'master' the unittest will fail
as they assume the default branch name is 'master'. Fix this
by explicitly set the intial branch name at 'git init'.
(Bitbake rev: 5bcd213c23da30a84baba88b775b1740e6bb77d0)
Signed-off-by: Peter Bergin <peter.bergin@windriver.com>
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current debug lists all the potential search paths but not the end result
which isn't helpful for debugging. Tweak to include the end result.
(Bitbake rev: a98b8dbb5fbd937a9530793485cf7c68fdd75cc2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To avoid confusion, rename the local fetcher localpaths function to
something more specific so it doesn't appear similar to the localpaths
top level function.
(Bitbake rev: ada5ea712cc42fff8c55bd261ee6d7579efd4a68)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Code changes for FILE_LAYERNAME exposed lifecycle issues around the collections
object in Cooker which only appeared in devtool usage in eSDK. Move
the collections setup to an earlier stage after parsing completes to
avoid any kind of race around it.
Also stop overwriting the code variable in MatchFiles. Ultimately we
need to combine these codepaths but that is for another patch.
(Bitbake rev: 27b872ed4fbe73b3b61e14cb885bb7c16c039cdb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The crate fetcher handles a crate with a name that matches the recipe's
name specially by placing the unpacked code in the current directory
(which typically is ${S}) rather than together with the sources for the
other crates. This broke when the URI names for all crates were changed
recently to include the version in the name.
Correct the crate fetcher to test against ${BP} instead of ${BPN}.
Also add a test case to the selftests to avoid this breaking again.
[Yocto #15012]
(Bitbake rev: 9af52b748357d0c843ce2507ce4d119fd9c37008)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If pstree in busybox is enabled there is a conflict with pstree from
psmisc resulting in:
do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If
the intention is to defer them to first boot, then please place
them into pkg_postinst_ontarget:${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
And more detailed in do_rootfs.log:
update-alternatives: Error: not linking [...]/rootfs/usr/bin/pstree to /bin/busybox.nosuid since [...]/rootfs/usr/bin/pstree exists and is not a link
On order to fix this set ALTERNATIVE:pstree accordingly.
(From OE-Core rev: deb2176df76dcb16c0d90072ad63d308a0ab1158)
Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* it was removed from SRC_URI in oe-core commit:
commit 67257ca87c6fa8e6050a20ecea50daf834c7e869
Author: Alexander Kanavin <alex.kanavin@gmail.com>
Date: Sat Apr 25 19:28:00 2020 +0200
Subject: rpm: upgrade to 4.15.1
and it's unused since then
(From OE-Core rev: c801a215fb2d53bdec7f4c9a20ff7969e8071e5c)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When running prepare_recipe_sysroot task, the extend_recipe_sysroot
is run twice.
What prepare_recipe_sysroot does is executing extend_recipe_sysroot,
there's no need to add extend_recipe_sysroot to its prefuncs.
(From OE-Core rev: bf7584a2ac16ee46ff5b41536b06bb46d0cbada7)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This matches the change in commit 139102a73d (recipes: Default to https
git protocol where possible), which did this for most recipes.
(From OE-Core rev: 21a06cb3f19570c65fc83d45069cab22136768b0)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When the protocol used to fetch the Git repository was changed from
"git" to "https" in commit 139102a73d (recipes: Default to https git
protocol where possible), the URI was not updated to match.
(From OE-Core rev: 0434a5ae168f737741e66a7fe1e30a8703b8ce16)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If both __NR_futex and __NR_futex_time64 are defined, g_futex_simple()
will first call futex_time64(). If that fails with ENOSYS, then
futex_time() is called instead. However, errno was not saved and
restored in this case, which would result in g_futex_simple()
returning with errno set to ENOSYS, even if futex_time() succeeded.
(From OE-Core rev: 1d6bff65391045ba40e84721eb0f6826e25e09f3)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream's dtb directory structure has no real standard. They just tend
to idle around the 2/3 directory depth. Recursively search for the
dtb/dtbo files instead of assuming anything.
Fixes: 04ab57d200 (kernel-devicetree: allow specification of dtb
directory, 2023-05-02)
(From OE-Core rev: 81570ba93eb282fd4566077d3b7b9ddf8c303002)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Depending on all of python3 (which pulls in all modules)
is not needed, python3-codecs is enough.
(From OE-Core rev: 718eda28f4f54d3033d2925e6c1232f4f8c2bc49)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
