This rebuilds whenever DISTRO_VERSION changes (i.e. any commit is made)
and systemd depends upon it so lots of things end up rebuilding which
isn't necessary,
(From OE-Core rev: 9d2eded1d423a24a8fa811f26d501bd68cd7a1be)
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>
(cherry picked from commit 002a2a9d977ed5b86138333c567d25616d38c60b)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
When run-postinsts is installed, a service is added for system which can run
while the package is still being installed. This calls "opkg configure" and if
package management is still running, it can deadlock and error.
To work around this, call fcntl-lock on the opkg lock file and if the lock
was held, it would wait to obtain it. This wait gives the package management
time to finish the install before the configure can then take the lock and run.
Note the dependency in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS otherwise we'd see
sstate selftest failures.
Also ensure that if the configure fails, the scripts returns an error. This
applies to opkg and dpkg.
(From OE-Core rev: 96d37df074dc1fe1578c1406235dff7e328b62b7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As we're close to release, drop compatibility to nanbield, people
have had time to switch now.
(From OE-Core rev: 0e42326dfd6b9042b405329ceb56a93199a89a85)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Prepare for the scarthgap release.
(From OE-Core rev: b1835e657575c29da43a15a37c673dc37044fd85)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a dependency which should have been in this list but wasn't, found
when debugging create-spdx hash issues.
(From OE-Core rev: 1075b9fc5d562dada45b3187cb737511ff8c7376)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OE-Core has changes which do need careful evaluation for compatibilty,
such as the addpylib directive. Move the core later names to mickledore
so layers can mark their compatibility as such.
Also increase the version number for core. If we do make further changes
that need layer changes, we'll update the version again so layers can mark
compatibility within the series.
(From OE-Core rev: 57239d66b933c4313cf331d35d13ec2d0661c38f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since bitbake now supports an official method to inject python modules,
switch to it.
Anyone using OE_EXTRA_IMPORTS will need to adjust their code accordingly,
probably switching to their own module namespace.
Also switch to using BB_GLOBAL_PYMODULES to list the global modules
to import.
(From OE-Core rev: 1f56155e91da2030ee0a5e93037c62e1349ba89f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Resurrect sato-icon-theme and move to a version with scalable icons support
to replace adwaita-icon-theme which no longer supports the icons we need
for the sato desktop.
(From OE-Core rev: 6b515037ab710adf7b2c14ae1bb488375655f311)
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>
Similarly to other tools such as pkgconfig and quilt, don't pull in
help2man-native unless there is a direct DEPENDS. This is generally good
for keeping the recipe sysroots leaner and cleaner and should fix some
issues with squashf-tools in particular.
This will mean any recipe with an indirect dependency will break so
missing recipe dependencies will need to be fixed.
(From OE-Core rev: df4e37ef888ad11f98c2f17ab4bc48dbd5417790)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Post release add langdale to the series names.
(From OE-Core rev: dc3b319a5fc47372bc111da5bc26d7dda1b17598)
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>
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>
There are several dependencies which recipes have which are not needed
at runtime, only at build time. Extend the list of these from bison to
include quilt, patch, meson, autoconf, automake and ninja which should
reduce the amount of data being included in native sysroots.
This speeds up and reduces the sstate needed for image builds for example.
If this change breaks recipes, it probably means they're missing an explicit
DEPENDS on something in this list which is a bug in the recipe.
(From OE-Core rev: 8e26252b45b7660c7c67c702411bdec187a76ffc)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to the override changes, we only allow compatibility with honister and
not hardknott.
(From OE-Core rev: 72c04cb3ca78208a135275d6dd43ad500b663cb5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The time has come to encourage people to update actively maintained
layers to use the new series name.
(From OE-Core rev: 737e3e608e64fc9ba67facc3dd2dd30497266f1e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit 05a87be51b44608ce4f77ac332df90a3cd2445ef introduced
a Python conditional expression when updating PATH that
generates syntax warnings in bitbake-cookerdaemon.log:
Var <PATH[:=]>:1: SyntaxWarning: "is not" with a literal. Did you mean "!="?
Fix this by using the more appropriate '!=' comparison
operator.
(From OE-Core rev: 2e753a12cf6bb98f9e0940e5ed6255ce8c538eed)
Signed-off-by: Matt Madison <matt@madison.systems>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sanity checker reports following error for the PATH variable,
when bitbake -e <recipe> command is run in an extensible SDK workspace.
PATH contains '.', './' or '' (empty element), which will break the build
In case of extensible SDK, PATH variable is formed with two consecutive ':'
as bb.utils.which(d.getVar('PATH'),'bitbake') call returns an empty string.
This change adds ':' if BITBAKEPATH is a non empty string.
(From OE-Core rev: 05a87be51b44608ce4f77ac332df90a3cd2445ef)
Signed-off-by: Sourabh Banerjee <sbanerje@codeaurora.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the core layer release series to gatesgarth in readiness for release.
(From OE-Core rev: d2e0d82f3e34a6c49066e39775572c5b8cd3c392)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Further to 5b2fd1c724
Also a few remaining references in comments and in distro_alias.inc
(From OE-Core rev: 35d4dd42477f316b6af889a0aec16439693e0849)
Signed-off-by: Douglas Royds <douglas.royds@taitradio.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
allarch is missing in ttf-bitstream-vera recipe. Add it and include the
recipe in the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS list.
(From OE-Core rev: 31c02477a4fb91f19f8c3ef3f8bc9a20e416c859)
Signed-off-by: Daniel Gomez <daniel@qtec.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
allarch package adwaita-icon-theme inherit both allarch and
gtk-icon-cache, since commit 31e3d34c8a9c3e8481aa837aa0bf52adf095fe62
[gtk-icon-cache.bbclass: add runtime dependency], it start depend on
non-allarch packages gdk-pixbuf and gtk+3, which make it's signature
changes when machine changed.
like for task do_prepare_recipe_sysroot:
"Hash for dependent task
gdk-pixbuf/gdk-pixbuf_2.40.0.bb:do_populate_sysroot changed from
a72aba8432699c8ce4ca1f71833ef14a89ffde0ea4063e37b9d819fdb1e407f4 to
1ad4e1bd76921b71482657f3b017184e9ade8e2a0b9f43ad64ed2dda83b1520f"
the only way to fix this is remove the task dependency.
SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS not work in class, so add it in
layer.conf.
Maybe we have other recipes under other layers have similar problem, we
can only add one by one to its layer.conf, seems not a good idea. but
add *->pixbuf will influence other packages
(From OE-Core rev: ec0888d73d7e7f811961f50f334c72fbc6b1d401)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The commits 910ffaf5be ("pyelftools: Import from meta-python") and
a96f815c53 ("pycryptodome: Import from meta-python") moved recipes from
meta-python to oe-core. In order for this to be communicated with users,
bump the LAYERVERSION so that meta-python can key of it in its
LAYERDEPENDS.
(From OE-Core rev: 2d503b27e7c88cee9a37c79c4605c77b11f230b6)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We're still compatible with dunfell from the core perspective so
that is left for compatibility (probably for the next week or two).
(From OE-Core rev: 1e79324f8290b820fee034b0d4a8c353027879da)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the layer core name to the new release name.
(From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These are added as dependencies by mime class, which could be inherited
along with allarch and dependencies silently go into target specific
recipes and which then can result in sstate hash signature mismatches
when the allarch recipes are reused for another arch
[YOCTO #13805]
(From OE-Core rev: 510015ac81df969f690d6c8661b00bebe73b7fca)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These changes are from meta-96boards primarily
Launch the session via a udev rule based on what kind of display device
is available
delete weston-conf and move the fuctionality into weston-init other
layers are doing same
weston-init installs machine specific weston.ini therefore mark is
machine specific now
(From OE-Core rev: aa3bced2e1de2f4ba507aa014835b06edccc138a)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The API between lttng-tools and lttng-modules is safe, whitelist it as
the dependency fixes tools failures. This needs a hack in the multilib
class as right now there is no way to know if a given recipe is a kernel
module or not. This needs to be revisited.
(From OE-Core rev: 584e713bf7f6885a13c440cd45c0f469feb3a694)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* import 2 fixes from LuneOS
* with l2tp PACKAGECONFIG enabled connman depends on MACHINE_ARCH xl2tpd:
=== Comparing signatures for task do_package_write_ipk.sigdata between hammerhead and mako ===
ERROR: connman different signature for task do_package_write_ipk.sigdata between hammerhead and mako
NOTE: Starting bitbake server...
Hash for dependent task xl2tpd/xl2tpd_git.bb.do_packagedata changed from 6312d5711b5c2c1a85ee235d09bf37a8ec00f7ad9e7248c087bb83ef1d5bd078 to c0d3ef52b37bda945d8b2a015980ddb8fe7b4b3dca3d82d71a84176cc5125142
Unable to find matching sigdata for /OE/build/luneos-master/webos-ports/meta-openembedded/meta-networking/recipes-protocols/xl2tpd/xl2tpd_git.bb.do_packagedata with hashes 6312d5711b5c2c1a85ee235d09bf37a8ec00f7ad9e7248c087bb83ef1d5bd078 or c0d3ef52b37bda945d8b2a015980ddb8fe7b4b3dca3d82d71a84176cc5125142
(From OE-Core rev: ba89fea0e443e1492000b7114f32edf15819a151)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The previous ccache.bbclass has the following problems:
- It uses host's ccache for native recipes, but this may not work on some
hosts, for example, it nerver works on my Ubuntu 14.04.4, there are always
build failures (m4-native failed at do_configure, and others will also be
failed if I disable CCACHE for m4-native)
- native/nativesdk/cross/crosssdk recipes use host's ccache, but target uses
ccache-native, this may confuse user.
- The target recipes may use both host's ccache and ccache-native, this may
cause unexpected problems and be hard to debug. This is because ccache-native is
in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS, so ccache-native may not be present when
rebuild target recipes, and then it would use hosttools/ccache, but the
previous ccache files were generated by ccache-native.
- Target recipes can't use ccache when no ccache is installed on the host:
CCACHE = "${@bb.utils.which(d.getVar('PATH'), 'ccache') and 'ccache '}"
After refactored:
All types recipes (native, target and others) will use ccache-native except
ccache-native itself, host's cache won't be used any more. It is more
reliable now, which will work everywhere when ccache-native can be built.
And now we need use "CCACHE_DISABLE = '1'" to disable ccache for the recipe
rather than "CCACHE = ''" since we set CCACHE in anonymous function, and
d.getVar('CCACHE') works after "CCACHE ??=" which is set in bitbake.conf, so we
can't check whether CCACHE is set or not in anonymous function since it is
always set. Use CCACHE_DISABLE to disable it would be more clear.
(From OE-Core rev: b25271b65262f70d849a4861da216c9be6c54d53)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We no longer have special "libc" for gcc so we can rely on plain
virtual/libc and reduce the complexity in the dependencies.
(From OE-Core rev: 122217b421f749b5fef52bea44ad6e04bc8f8d3a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Weston needs to be configured to load the fbdev driver when run on a QEMU system.
Other MACHINEs may want to also provider their own configuration as well..
Adding a new RRECOMMEND configuration package will allow this, but avoid
installing empty packages/files in the majority case where it is not needed.
Add maintainer entry as well.
(From OE-Core rev: 0f43ea8510ae6148a49eb25accac407b6b301b43)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Create a new systemd-conf recipe to contain the specific system/machine
configuration items. This new package is now machine specific.
Without doing this trying to create a single system with multiple BSPs,
one of which was qemu based, would result in the systemd -and- everything that
dependend upon systemd to have their hash changed. The hash changing means
lots of rebuilds, but worse if it's a package based system each different
machine ends with a new PR value and a newly generated package.
(From OE-Core rev: d3395418758ed414eee3e95e13d2d8bc5dca88cc)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Prepare for release and drop sumo for the compatible list of layer names.
This will mean other layers need updating to continue to indicate compatibility
with master but that is intentional at this part of the release cycle, we want
layers to indicate compatibility and show they're up to date.
(From OE-Core rev: 9ec5a8a0f86510f7aae572dfb79e8bda73d4e0fc)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the release approaching, add thud to LAYERSERIES_CORENAMES and update
oe-core to use this release series. "sumo" will be removed during M4 in
the next couple of weeks so people need to start updating their master
layers in preperation for release.
(From OE-Core rev: 986792481fa005fe136fd4b4e388042492b1ad8a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
remove the indirect dependcy of autoconf-archive-native via
SSTATE_EXCLUDEDEPS_SYSROOT to avoid not needed .m4 installed
into sysroot, which may cause compile problem.
(From OE-Core rev: d23156460e2b8f6684bd3005d7fa09b2c73e522e)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Avoid adding bison-native to the sysroot without a specific
dependency in the recipe. This means indirect dependencies
(e.g. X -> Y -> binutils-cross -> bison-native) no longer meet the
dependency incidentally. This improves determinism and avoids build
failures when people switch to external toolchains.
Based on an idea by Richard Purdie:
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146324.html
(From OE-Core rev: b7edc20cc2dd82989bd9561f860cb25478a40f69)
Signed-off-by: André Draszik <andre.draszik@jci.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use the newly introduced SSTATE_EXCLUDEDEPS_SYSROOT for specifying
the base-passwd|shadow-sysroot recipes to be excluded from a recipe sysroot.
(From OE-Core rev: 68e502e9063a88532fe0154f152ba408f0091900)
Signed-off-by: André Draszik <andre.draszik@jci.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
