public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: "Moessbauer, Felix (T CED SES-DE)" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH] base: Fix HOST_ARCH for native builds
Date: Thu, 21 Sep 2023 08:57:00 +0300	[thread overview]
Message-ID: <60b834aa4705395fc0a39871ac902666b9fec4a0.camel@ilbers.de> (raw)
In-Reply-To: <17edc64a-b2dd-4219-8b03-62362d367665@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 2466 bytes --]

On Mon, 2023-09-18 at 10:04 +0200, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> HOST_ARCH must be DISTRO_ARCH when we are not cross-building.
> Otherwise,
> recipes that set PACKAGE_ARCH to it will fail in native builds.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Affects specifically the starfive packages.
> 
>  meta/classes/base.bbclass | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index 88004120..f315a9d5 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -49,13 +49,15 @@ def oe_import(d):
>  # We need the oe module name space early (before INHERITs get added)
>  OE_IMPORTED := "${@oe_import(d)}"
>  
> -def get_deb_host_arch():
> +def get_deb_host_arch(d):
>      import subprocess
> +    if d.getVar("ISAR_CROSS_COMPILE") != "1":
> +        return d.getVar("DISTRO_ARCH")
>      host_arch = subprocess.check_output(
>          ["dpkg", "--print-architecture"]
>      ).decode('utf-8').strip()
>      return host_arch
> -HOST_ARCH ??= "${@get_deb_host_arch()}"
> +HOST_ARCH ??= "${@get_deb_host_arch(d)}"
>  HOST_DISTRO ??= "${DISTRO}"
>  
>  die() {
> -- 
> 2.35.3
> 

With this patch CI fails in several tests at parsing stage in case few
"too different" multiconfigs are built in parallel:

For example, ReproTest.test_repro_unsigned:

```
[stdout] ERROR: /workspace/build/isar_ub_devel/317/meta-isar/recipes-
core/images/isar-image-debug.bb: Overrides could not be expanded into a
stable state after 5 iterations, overrides must be being referenced by
other overridden variables in some recursive fashion. Please provide
your configuration to bitbake-devel so we can laugh, er, I mean try and
understand how to make it work.
[stdlog] 2023-09-20 14:06:26,962 avocado.app ERROR| ERROR:
/workspace/build/isar_ub_devel/317/meta-isar/recipes-core/images/isar-
image-debug.bb: Overrides could not be expanded into a stable state
after 5 iterations, overrides must be being referenced by other
overridden variables in some recursive fashion. Please provide your
configuration to bitbake-devel so we can laugh, er, I mean try and
understand how to make it work.
```

I'm attaching kas config that easy reproduces the issue. When changed
"refspec" to "next", it works.



[-- Attachment #2: fix-host-arch-issue.yml --]
[-- Type: application/x-yaml, Size: 549 bytes --]

  reply	other threads:[~2023-09-21  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  8:04 Jan Kiszka
2023-09-21  5:57 ` Uladzimir Bely [this message]
2023-09-21 10:36   ` 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=60b834aa4705395fc0a39871ac902666b9fec4a0.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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