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 v3] base: Fix HOST_ARCH for native builds
Date: Tue, 03 Oct 2023 19:11:12 +0300	[thread overview]
Message-ID: <7e07f179fc044f58158a602e8fb2dd4b7f545c0d.camel@ilbers.de> (raw)
In-Reply-To: <7e817969-de10-43fa-911d-639aa91e9499@siemens.com>

On Sun, 2023-10-01 at 11:09 +0200, Jan Kiszka 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.
> 
> To avoid recursions, we have to rework the ISAR_CROSS_COMPILE setting
> in
> imagetypes.bbclass to an anonymous python function.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> This looks better now.
> 
> Maybe we can even kill BUILD_HOST_ARCH, now that HOST_ARCH is fixed.
> 
>  meta/classes/base.bbclass       | 6 ++++--
>  meta/classes/imagetypes.bbclass | 6 ++++--
>  2 files changed, 8 insertions(+), 4 deletions(-)
> 
Applied to next, thanks.

  reply	other threads:[~2023-10-03 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01  9:09 Jan Kiszka
2023-10-03 16:11 ` Uladzimir Bely [this message]
2023-10-05  5:48 ` Uladzimir Bely
2023-10-05  6:56   ` Jan Kiszka
2023-10-05  8:18     ` Uladzimir Bely
2023-10-05  8:36     ` Jan Kiszka
2023-10-05  9:37       ` Jan Kiszka
2023-10-05 10:17         ` Uladzimir Bely
2023-10-05 10:39           ` 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=7e07f179fc044f58158a602e8fb2dd4b7f545c0d.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