From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schild, Henning" <henning.schild@siemens.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"ibr@ilbers.de" <ibr@ilbers.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: RE: [PATCH v4 1/2] run imager in buildchroot-host on cross
Date: Thu, 15 Sep 2022 09:35:38 +0000 [thread overview]
Message-ID: <AM9PR10MB48694A3330418B620518AD5089499@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <bf8715ac-83ba-a37d-c122-ef9ecd01c107@ilbers.de>
> -----Original Message-----
> From: Anton Mikanovich <amikan@ilbers.de>
> Sent: Thursday, September 15, 2022 11:14 AM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>; isar-
> users@googlegroups.com
> Cc: Schild, Henning (T CED SES-DE) <henning.schild@siemens.com>; Schmidt,
> Adriaan (T CED SES-DE) <adriaan.schmidt@siemens.com>; ibr@ilbers.de; Kiszka,
> Jan (T CED) <jan.kiszka@siemens.com>
> Subject: Re: [PATCH v4 1/2] run imager in buildchroot-host on cross
>
> 14.09.2022 23:21, Felix Moessbauer wrote:
> > When globally enabling ISAR_CROSS_COMPILE, the imager and compression
> > tasks run in the host buildchroot as well (instead of the target
> > buildchroot).
> >
> > Similar to the cross support for DPKG recipes, this can be toggled on
> > a per-image basis by setting ISAR_CROSS_COMPILE in the image recipe.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
>
> Hello Felix,
>
> This actually brakes SDK building for amd64 stretch targets because there is no
> crossbuild-essential-amd64 there.
Hi,
Interesting finding.
Are there any CI tests that catch this? At least I cannot find a CROSS test that builds the SDK.
Apart from that, Debian stretch is EOL since June 22.
I'm fine with keeping the stretch targets, but then we could simply disable CROSS by setting
ISAR_CROSS_COMPILE_debian-stretch = "0" in the image.bbclass.
If you could point me to a target for testing, I'm happy to add that.
Best regards,
Felix
next prev parent reply other threads:[~2022-09-15 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 20:21 [PATCH v4 0/2] use xz and gzip on host (outside chroot) Felix Moessbauer
2022-09-14 20:21 ` [PATCH v4 1/2] run imager in buildchroot-host on cross Felix Moessbauer
2022-09-15 9:14 ` Anton Mikanovich
2022-09-15 9:35 ` Moessbauer, Felix [this message]
2022-09-15 10:45 ` Anton Mikanovich
2022-09-15 11:04 ` Moessbauer, Felix
2022-09-15 11:06 ` Henning Schild
2022-09-15 15:43 ` Anton Mikanovich
2022-09-15 11:08 ` Henning Schild
2022-09-15 15:44 ` Anton Mikanovich
2022-09-15 17:08 ` Moessbauer, Felix
2022-09-16 7:41 ` Anton Mikanovich
2022-09-14 20:21 ` [PATCH v4 2/2] add wic.xz image to qemuarm64-bookworm Felix Moessbauer
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=AM9PR10MB48694A3330418B620518AD5089499@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--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