From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7285724351391858688 X-Received: by 2002:ac2:58d0:0:b0:503:17fd:76bb with SMTP id u16-20020ac258d0000000b0050317fd76bbmr10455658lfo.39.1696347546982; Tue, 03 Oct 2023 08:39:06 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:651c:4d2:b0:2bf:c704:bca1 with SMTP id e18-20020a05651c04d200b002bfc704bca1ls382013lji.0.-pod-prod-04-eu; Tue, 03 Oct 2023 08:39:04 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHrdhbQjZZ5UD+PgujIVi50vfoKzPAVRVA2FaqKQGqFcXJTnVdDcfoUdFC+9nGtvpf55oVw X-Received: by 2002:a05:6512:3608:b0:4f9:54f0:b6db with SMTP id f8-20020a056512360800b004f954f0b6dbmr10556878lfs.13.1696347544542; Tue, 03 Oct 2023 08:39:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696347544; cv=none; d=google.com; s=arc-20160816; b=KYc8xVtQ8U5Snbp+b73WkqWtvVizmwVGdNr3ACxtQblLguuCPJU/gqRt7ekUGipkZy AtSrK0cEiLEvxGEBsNKlXe21oEE4Z6R9I0EqGCvXPA8BDqK9LTIZvHrTE5GzmaYOSsDE JZ4Ei4get4JuS8pewKf7ZksqQ6lcbPedO4QcoURLiNEK5Zhd1mH1KOH245eIe61DqzKU SMenvnl1RiDHfdRKxmHG4DyqFgtk3h3dApmp4ynUevToTZzO/vK353IuPv44QEClEJ3i InZPifbXxxx+sE07U5dCss2X8o4sXMxBV3RrzqPMudsVUD0YMlLBTakx3UpXM3MQgbPP /+8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id; bh=cASLC0ZEajSo/q+/ZPK5CC8OJP1iEsOuCSdi6VRUanE=; fh=Wti97AxnB8o6F4p4MVfzofhb0hZGnJ5kIdomD/OtAzE=; b=dQJQ+/+rO8Tha6SwRUl2XriDmijsZ3vA0xpTaEnIyEOB5/7E37Jr34/V7XIQnu9IXB 0he/IX+oFXjfnN6nIF6pPr6wXQGMUe2m5h19zoN4CmlDZzCDxVf8zUytNRVc5lyAL0Nn IJVU5o0h5rHX0NUKU1sQI+G4L/NN2Ufgl8VT4eDxLZ3v3//ht/COY8dNjsAVTee7vqJU tglGXhjTvjuGQXnezbqDlUXS7ZF8u67aEP0kxrQuIavkxRoHiNNuQ4DwWMpEBgJVky9r FUuWDp/KIFgal6cVmS7Fb5A2Il3FPCNuZewdawqGRlcKxGZQtadUp4ZutWMyy9i5PuI+ mFUA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id u3-20020ac258c3000000b004fbcd4b8b84si122440lfo.0.2023.10.03.08.39.04 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 03 Oct 2023 08:39:04 -0700 (PDT) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from [127.0.0.1] (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 393Fcl5C018600 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 3 Oct 2023 17:39:02 +0200 Message-ID: Subject: Re: SSTATE cache not working for -native recipes due to unexpanded variable From: Uladzimir Bely To: "Waltl, Jan" , "isar-users@googlegroups.com" Date: Tue, 03 Oct 2023 18:41:07 +0300 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (by Flathub.org) MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: IVebqUGxgqiI On Tue, 2023-10-03 at 13:30 +0000, 'Waltl, Jan' via isar-users wrote: > Hello, >=20 > 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. >=20 > Reproduction steps: > 1. Checkout ISAR next 216f0721265fcfe965ac48b51a0128d612d89bf4. > 2. Run 'bitbake cowsay-native' from meta-isar layer=C2=A0 (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:311a86032fcbd98d2343b40447e0558b5aae410ff64f727ae5 > 6aa2952167f05e_patch.tar.zst.siginfo > sstate-cache/3b/24/sstate:cowsay- > native::git:r0::10:3b2452fa0b072ed1488aad9432257dff8bee324659b5f0738a > b224d82b1de2fc_unpack.tar.zst.siginfo > sstate-cache/d6/ab/sstate:cowsay- > native::git:r0::10:d6abcc3328b93b67b59ef9c0b21449188f1330bc76d6ee6372 > c76e94bec87756_fetch.tar.zst.siginfo > sstate-cache/isarnative/64/de/sstate:cowsay-native:amd64- > isar:git:r0:${SSTATE_PKGARCH}:10:64de5a007fac75eebd427a2ea9156cf01427 > 18f68362a06b51c65559fc8045b7_dpkg_build.tar.zst.siginfo' > sstate-cache/isarnative/64/de/sstate:cowsay-native:amd64- > isar:git:r0::10:64de5a007fac75eebd427a2ea9156cf0142718f68362a06b51c65 > 559fc8045b7_dpkg_build.tar.zst > sstate-cache/isarnative/aa/07/sstate:cowsay-native:amd64- > isar:git:r0:${SSTATE_PKGARCH}:10:aa07cf2e6ff17f7004e6dc2b4e7a9a6123b1 > 27668c27d4c3cb29d0f7dc65ac5f_deploy_deb.tar.zst.siginfo' > sstate-cache/isarnative/c4/db/sstate:cowsay-native:amd64- > isar:git:r0:${SSTATE_PKGARCH}:10:c4dbfbe1c1696f2b690f15cbd179a5795fe4 > 8f05a30a76d20783c98786af6d4a_adjust_git.tar.zst.siginfo' > sstate-cache/isarnative/d0/0c/sstate:cowsay-native:amd64- > isar:git:r0:${SSTATE_PKGARCH}:10:d00c69fa102b131bc09fb27aa8259fcb447d > be5b51d5f6723d1e12ff43f92fee_transform_template.tar.zst.siginfo' > sstate-cache/isarnative/e7/94/sstate:cowsay-native:amd64- > isar:git:r0:${SSTATE_PKGARCH}:10:e794e52fe10ccf60b559089c39eaf86a4990 > a81991c9b1b0b2672721878a1b8b_prepare_build.tar.zst.siginfo' >=20 > 5. Remove stamps directory. > 6. Build again - SSTATE should be used for the package but it is not > and the tasks are run again. >=20 > I think it is related to > https://github.com/ilbers/isar/blob/61086915e6c83fff22effa85cda64a2ac0c2f= 100/meta/classes/sstate.bbclass#L136 > =C2=A0and BUILD_ARCH being empty according to 'bitbake -e'.=20 >=20 > I changed the line to HOST_ARCH (+expand=3DTrue) 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? >=20 > How to best resolve this? >=20 >=20 Hello, Jan. I've tried to repeat your steps and reproduced the issue in case of cross-building. Changing the line to HOST_ARCH is techincally correct. But since we don't like forking (sstate.bbclass is taken from some OE branch without any changes), I think it would be better to just define BUILD_ARCH somewhere else in Isar to the value of HOST_ARCH, for example: diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 9eb93e2b..0d737b64 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -90,6 +90,7 @@ NATIVELSBSTRING ?=3D "isarnative" TARGET_VENDOR =3D "" TARGET_OS =3D "isar" PACKAGE_ARCH ?=3D "${DISTRO_ARCH}" +BUILD_ARCH ?=3D "${HOST_ARCH}" =20 # Isar apt repository paths REPO_ISAR_DIR =3D "${DEPLOY_DIR}/isar-apt/${DISTRO}-${DISTRO_ARCH}/apt" This seems to work and doesn't fork sstate.bbclass, so it can be later updated to some newer OE revision. Unfortunately, HOST_ARCH has different meanings in Isar and Yocto... > [This is my first message to this mailing list, please correct me if > I am doing something wrong] >=20 >=20 > Kind Regards, > Jan Waltl >=20 > Siemens Mobility, s.r.o. > SMO RI LCE CZ SAF 1 >=20 >=20 >=20