public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	isar-users <isar-users@googlegroups.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: WARNING: Isar cross building fails
Date: Fri, 19 Aug 2022 22:24:17 +0200	[thread overview]
Message-ID: <a20899bb-6bb4-bf49-7abf-296979ae0781@siemens.com> (raw)
In-Reply-To: <76b3958b-77b1-0632-dde0-f85a5551ec68@ilbers.de>

On 19.08.22 09:37, Anton Mikanovich wrote:
> Hello,
> 
> Just want to notify Isar is failing on cross compile build of any packages
> currently. This is probably caused by upstream repo changes, we are already
> working on that issue.
> 

What do you mean by upstream repo changes? The libc update in Debian
bookworm that did not cover all architectures yet?

I can confirm some cross-compiling issues on bookworm, but not on stable
(bullseye).

Best regards,
Florian

  reply	other threads:[~2022-08-19 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  7:37 Anton Mikanovich
2022-08-19 20:24 ` Florian Bezdeka [this message]
2022-08-22  8:11   ` Anton Mikanovich
2022-08-22  8:38     ` Bezdeka, Florian

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=a20899bb-6bb4-bf49-7abf-296979ae0781@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --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