From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Fix problem with leftover files in tmp/sysroots-components
Date: Fri, 6 Apr 2018 20:26:54 +0200 [thread overview]
Message-ID: <cover.1523039141.git.pkj@axis.com> (raw)
We have seen problems where sometimes files are leftover in
tmp/sysroots-components when changing PACKAGE_ARCH for a package. This
could then lead to those files being picked up instead of the real
files when the RSS for another package was created.
It turned out that this happened if the original architecture of the
package was one that was added using PACKAGE_EXTRA_ARCHS. Those extra
architectures were not handled in the sstate_eventhandler2() function
in sstate.bbclass that does the clean up of tmp/sysroots-components.
During the course of debugging this problem I also noticed that there
were two index files in tmp/sstate-control for machines that contain a
dash in their names. This turned out to be due to the use of the
stamp-extra-info task flag for some tasks, which were using ${MACHINE}
rather than ${MACHINE_ARCH} to specify the architecture. Since this
seemed inconsistent and confusing, I fixed that as well.
//Peter
The following changes since commit 312a5a93cac95fe62c56e374db728c825b272e64:
layer.conf: Update LAYERSERIES rocko -> sumo (2018-04-06 11:39:49 +0100)
are available in the git repository at:
git://push.yoctoproject.org/poky-contrib pkj/extra-archs-in-sstate
Peter Kjellerstedt (3):
Use ${MACHINE_ARCH} instead of ${MACHINE} for stamp-extra-info task
flag
sstate.bbclass: Add ${PACKAGE_EXTRA_ARCHS} to SSTATE_ARCHS
license.bbclass: Minor simplification of get_deployed_dependencies()
meta/classes/deploy.bbclass | 2 +-
meta/classes/image.bbclass | 2 +-
meta/classes/license.bbclass | 4 +---
meta/classes/package.bbclass | 2 +-
meta/classes/populate_sdk_base.bbclass | 2 +-
meta/classes/populate_sdk_ext.bbclass | 2 +-
meta/classes/sstate.bbclass | 5 +++--
meta/recipes-core/meta/signing-keys.bb | 3 ++-
8 files changed, 11 insertions(+), 11 deletions(-)
--
2.12.0
next reply other threads:[~2018-04-06 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 18:26 Peter Kjellerstedt [this message]
2018-04-06 18:26 ` [PATCH 1/3] Use ${MACHINE_ARCH} instead of ${MACHINE} for stamp-extra-info task flag Peter Kjellerstedt
2018-04-06 18:26 ` [PATCH 2/3] sstate.bbclass: Add ${PACKAGE_EXTRA_ARCHS} to SSTATE_ARCHS Peter Kjellerstedt
2018-04-06 18:26 ` [PATCH 3/3] license.bbclass: Minor simplification of get_deployed_dependencies() Peter Kjellerstedt
2018-04-06 18:34 ` ✗ patchtest: failure for Fix problem with leftover files in tmp/sysroots-components Patchwork
2018-04-06 18:53 ` Peter Kjellerstedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1523039141.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox