From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"ibr@ilbers.de" <ibr@ilbers.de>
Subject: Re: WARNING: Isar cross building fails
Date: Mon, 22 Aug 2022 08:38:15 +0000 [thread overview]
Message-ID: <4d730d4368048ccb708b170cce44c49fab2e3111.camel@siemens.com> (raw)
In-Reply-To: <6330005f-c818-e3d6-aa95-d3d3bf105826@ilbers.de>
On Mon, 2022-08-22 at 11:11 +0300, Anton Mikanovich wrote:
> 19.08.2022 23:24, Florian Bezdeka wrote:
> > 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
>
> Hello Florian,
>
> Yes, bullseye is building ok at least on armhf target, but bookworm is not.
> It starts after the latest libc6-dev dependencies changes (2.33-8 ->
> 2.34-3) which made
> deps resolver inside sbuild proccess fail on
> "libc6-dev-armhf-cross:amd64 (< 2.34~)" + "libc6-dev-armhf-cross:amd64
> (>= 2.23-1~)"
> for some reason.
I looked at that for some minutes and gave up. The problem vanished,
seems all mirrors and architectures are in sync now.
>
> As a temporary hotfix setting ISAR_CROSS_COMPILE = "0" can be used.
>
prev parent reply other threads:[~2022-08-22 8:38 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
2022-08-22 8:11 ` Anton Mikanovich
2022-08-22 8:38 ` Bezdeka, Florian [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=4d730d4368048ccb708b170cce44c49fab2e3111.camel@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