From: "Waltl, Jan" <jan.waltl@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: SSTATE cache not working for -native recipes due to unexpanded variable
Date: Tue, 3 Oct 2023 13:30:23 +0000 [thread overview]
Message-ID: <AM9PR10MB432206DA0015A8A06C6AE5EDF6C4A@AM9PR10MB4322.EURPRD10.PROD.OUTLOOK.COM> (raw)
Hello,
I noticed that for -native recipes, SSTATE_PKGARCH variable is not expanded in the .siginfo filename. On rebuild, SSTATE reports mismatches leading to rebuilds even though the recipe and the resulting stamps are exactly the same.
Reproduction steps:
1. Checkout ISAR next 216f0721265fcfe965ac48b51a0128d612d89bf4.
2. Run 'bitbake cowsay-native' from meta-isar layer (I use KAS for setting up the bitbake directory)
4. Look into sstate directory, I see a files:
sstate-cache/31/1a/sstate:cowsay-native::git:r0::10:311a86032fcbd98d2343b40447e0558b5aae410ff64f727ae56aa2952167f05e_patch.tar.zst.siginfo
sstate-cache/3b/24/sstate:cowsay-native::git:r0::10:3b2452fa0b072ed1488aad9432257dff8bee324659b5f0738ab224d82b1de2fc_unpack.tar.zst.siginfo
sstate-cache/d6/ab/sstate:cowsay-native::git:r0::10:d6abcc3328b93b67b59ef9c0b21449188f1330bc76d6ee6372c76e94bec87756_fetch.tar.zst.siginfo
sstate-cache/isarnative/64/de/sstate:cowsay-native:amd64-isar:git:r0:${SSTATE_PKGARCH}:10:64de5a007fac75eebd427a2ea9156cf0142718f68362a06b51c65559fc8045b7_dpkg_build.tar.zst.siginfo'
sstate-cache/isarnative/64/de/sstate:cowsay-native:amd64-isar:git:r0::10:64de5a007fac75eebd427a2ea9156cf0142718f68362a06b51c65559fc8045b7_dpkg_build.tar.zst
sstate-cache/isarnative/aa/07/sstate:cowsay-native:amd64-isar:git:r0:${SSTATE_PKGARCH}:10:aa07cf2e6ff17f7004e6dc2b4e7a9a6123b127668c27d4c3cb29d0f7dc65ac5f_deploy_deb.tar.zst.siginfo'
sstate-cache/isarnative/c4/db/sstate:cowsay-native:amd64-isar:git:r0:${SSTATE_PKGARCH}:10:c4dbfbe1c1696f2b690f15cbd179a5795fe48f05a30a76d20783c98786af6d4a_adjust_git.tar.zst.siginfo'
sstate-cache/isarnative/d0/0c/sstate:cowsay-native:amd64-isar:git:r0:${SSTATE_PKGARCH}:10:d00c69fa102b131bc09fb27aa8259fcb447dbe5b51d5f6723d1e12ff43f92fee_transform_template.tar.zst.siginfo'
sstate-cache/isarnative/e7/94/sstate:cowsay-native:amd64-isar:git:r0:${SSTATE_PKGARCH}:10:e794e52fe10ccf60b559089c39eaf86a4990a81991c9b1b0b2672721878a1b8b_prepare_build.tar.zst.siginfo'
5. Remove stamps directory.
6. Build again - SSTATE should be used for the package but it is not and the tasks are run again.
I think it is related to https://github.com/ilbers/isar/blob/61086915e6c83fff22effa85cda64a2ac0c2f100/meta/classes/sstate.bbclass#L136 and BUILD_ARCH being empty according to 'bitbake -e'.
I changed the line to HOST_ARCH (+expand=True) which seems to work but I do not have enough expertise to guess its correctness. Maybe the line in native.bbclass covers this "if statement" already?
How to best resolve this?
[This is my first message to this mailing list, please correct me if I am doing something wrong]
Kind Regards,
Jan Waltl
Siemens Mobility, s.r.o.
SMO RI LCE CZ SAF 1
next reply other threads:[~2023-10-03 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 13:30 Waltl, Jan [this message]
2023-10-03 15:41 ` Uladzimir Bely
2023-10-06 7:59 ` Waltl, Jan
2023-10-07 6:05 ` MOESSBAUER, Felix
2023-10-07 6:12 ` Jan Kiszka
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=AM9PR10MB432206DA0015A8A06C6AE5EDF6C4A@AM9PR10MB4322.EURPRD10.PROD.OUTLOOK.COM \
--to=jan.waltl@siemens.com \
--cc=isar-users@googlegroups.com \
/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