public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "Bovensiepen, Daniel (bovi)" <daniel.bovensiepen@siemens.com>
Subject: Re: debian-sid build for RISCV64 broken
Date: Fri, 10 Nov 2023 08:37:51 +0000	[thread overview]
Message-ID: <0916dd133ed93290efadba8ec242366c89ddc8b3.camel@siemens.com> (raw)
In-Reply-To: <eb0e9f1e-3655-424b-8d9a-fe91d49deca4@siemens.com>

On Fri, 2023-11-10 at 09:22 +0100, Jan Kiszka wrote:
> On 10.11.23 09:13, 'MOESSBAUER, Felix' via isar-users wrote:
> > Dear devs,
> > 
> > we currently cannot build the riscv64 targets, as the sbuild chroot
> > packages have conflicting internal dependencies. This happens quite
> > frequently due to updates to the upstream sid repositories.
> > 
> > I'm wondering if we should pin riscv64 to snapshots.debian.org to
> > avoid
> > these breaks. However, there we are rate-limited, making our builds
> > rather slow / unstable.
> > 
> > I'm open for other approaches, but would highly appreciate if we
> > could
> > have a stable riscv64 build.
> > 
> 
> RISC-V crossbuilding is broken, and is expected to remain broken for
> some more month according to what I heard from Debian folks. Native
> building against sid worked the last time I tried, but it's not
> practical for anything that needs an own kernel etc.

Yes, for all practical use-cases we must have cross support.
Do we have any references that state this? Can we somehow get involved
to speedup fixing this?

> 
> Using snapshot means going back to early this year, using sid-ports
> again - while it is also not working reliably due to server issues
> and
> throttling of that service. That's what we are stuck with on
> isar-cip-core side.

This is more or less a showstopper for any work on porting things to
riscv64 in debian. We cannot even do prototypical porting of
applications anymore, as things simply don't build. What a bummer.

In the past it was at least somehow stable and could be used for
prototyping.

Felix

> 
> Jan
> 


  reply	other threads:[~2023-11-10  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10  8:13 MOESSBAUER, Felix
2023-11-10  8:22 ` Jan Kiszka
2023-11-10  8:37   ` MOESSBAUER, Felix [this message]
2023-11-10  8:44     ` 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=0916dd133ed93290efadba8ec242366c89ddc8b3.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=daniel.bovensiepen@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