From: Jan Kiszka <jan.kiszka@siemens.com>
To: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: -native working as designed? target vs host sbuild-chroot
Date: Fri, 6 Oct 2023 07:20:51 +0200 [thread overview]
Message-ID: <c5f17af1-4dd1-4d51-a514-eebe439bbc02@siemens.com> (raw)
In-Reply-To: <207e5270-361a-478b-bfb1-0eccd72ef1a0@siemens.com>
On 06.10.23 04:49, 'cedric.hombourger@siemens.com' via isar-users wrote:
> Hello,
>
> I was wondering if handling of -native was working as designed (or if I
> am missing something).
>
> Let's consider the following steps:
>
> git clone -b next https://github.com/ilbers/isar
> . isar-init-build-env
This gives your ISAR_CROSS_COMPILE = 0.
> mc:qemuarm64-bookworm:hello-native
This is similar to the issue I'm trying to fix with my patch series sent
yesterday evening: 'hello-native' in a non-cross environment should
actually be 'hello' because non-cross means that there is no separate
host build env. My patches will resolve that contradiction, but only for
dependencies you have in your recipes, not for explicitly requested
builds. I'm not sure if we can and should do anything about such
explicit requests.
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-10-06 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 2:49 cedric.hombourger
2023-10-06 4:59 ` Schmidt, Adriaan
2023-10-06 5:03 ` cedric.hombourger
2023-10-06 5:27 ` Jan Kiszka
2023-10-06 6:17 ` cedric.hombourger
2023-10-06 12:02 ` Jan Kiszka
2023-10-06 12:12 ` Jan Kiszka
2023-10-06 12:30 ` Jan Kiszka
2023-10-06 14:56 ` cedric.hombourger
2023-10-06 15:19 ` Jan Kiszka
2023-10-06 5:20 ` 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=c5f17af1-4dd1-4d51-a514-eebe439bbc02@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=cedric.hombourger@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