From: Jan Kiszka <jan.kiszka@siemens.com>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"Waltl, Jan" <jan.waltl@siemens.com>,
"ubely@ilbers.de" <ubely@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: SSTATE cache not working for -native recipes due to unexpanded variable
Date: Sat, 7 Oct 2023 08:12:36 +0200 [thread overview]
Message-ID: <314c9203-7dd7-4804-8ad0-8fd83c8615f6@siemens.com> (raw)
In-Reply-To: <15ad3c56b2be6ce2dacc5fb09db6652efcbafa5c.camel@siemens.com>
On 07.10.23 08:05, 'MOESSBAUER, Felix' via isar-users wrote:
> On Fri, 2023-10-06 at 07:59 +0000, 'Waltl, Jan' via isar-users wrote:
>> Hello Uladzimir,
>>
>> Thank you very, the patch appears to fix the issue for caching of
>> native builds for me - now SSTATE works with them.
>>
>> Also, I see some related discussions on the mailing list I will try
>> to follow.
>
> I guess this is actually related to the inverse meaning of HOST_ARCH
> and DISTRO_ARCH in Yocto and GNU / ISAR. By that, I vote for the patch
> proposed by Uladzimir.
>
> @Jan: Could you please send this patch to the ML and put Adriaan in CC,
> as he implemented most of the sstate parts for ISAR.
Are you referring to
https://groups.google.com/d/msgid/isar-users/60dba7199afdc8b71494b55081b1193e091b9bde.1696606502.git.jan.kiszka%40siemens.com
?
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-10-07 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 13:30 Waltl, Jan
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 [this message]
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=314c9203-7dd7-4804-8ad0-8fd83c8615f6@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.waltl@siemens.com \
--cc=ubely@ilbers.de \
/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