all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org,  guix-sysadmin <guix-sysadmin@gnu.org>
Subject: Re: RISC-V (riscv64-linux) substitutes are coming
Date: Tue, 09 May 2023 17:20:24 +0200	[thread overview]
Message-ID: <875y91o7k7.fsf@gnu.org> (raw)
In-Reply-To: <87v8h1396k.fsf@cbaines.net> (Christopher Baines's message of "Tue, 09 May 2023 14:40:21 +0100")

Christopher Baines writes:

Hi Chris,

> Almost a year ago now [1] I mentioned that I had received a HiFive
> Unmatched board, but I hadn't got it doing anything yet.
>
> 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html
>
> In the last few days I've made some time to take a look at it again and
> try to get it connected up to the bordeaux build farm.
>
> This has been somewhat successful, you should be able to see the machine
> (named rochor) on the prototype activity viewer [2].

That's lovely!  Because of my the Mes release that should have initial
RISC-V support I've been looking for RISC-V substitutes.  The good folks
over at #bootstrappable advised me to just build using QEMU, the
consensus was that gave dependable results....

However, I found that many packages have failing tests, mostly related
to stack (overflow) checks.  I looked at wip-riscv but that seems to be
1.5y old...so I've building and disabling tests over at

    https://gitlab.com/janneke/guix/-/tree/wip-riscv

Hopefully all this isn't necessary when using real RISC-V hardware!

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com


  parent reply	other threads:[~2023-05-09 15:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 13:40 RISC-V (riscv64-linux) substitutes are coming Christopher Baines
2023-05-09 14:09 ` Efraim Flashner
2023-05-09 14:22   ` Christopher Baines
2023-05-09 15:24     ` Aleksandr Vityazev
2023-05-09 15:41       ` Christopher Baines
2023-05-09 18:33         ` Aleksandr Vityazev
2023-05-09 15:57       ` Efraim Flashner
2023-05-09 16:26         ` Aleksandr Vityazev
2023-05-09 14:19 ` 宋文武
2023-05-09 14:27   ` Christopher Baines
2023-05-10 12:44     ` 宋文武
2023-05-13  3:34       ` 宋文武
2023-05-13  3:49         ` 宋文武
2023-05-13 10:15         ` 宋文武
2023-05-09 14:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-09 14:33   ` Christopher Baines
2023-05-09 15:20 ` Janneke Nieuwenhuizen [this message]
2023-05-10  9:05 ` Andreas Enge
2023-05-10  9:24   ` Christopher Baines
2023-05-11 11:15 ` 郑俊杰
2023-05-12 16:35 ` Z572
2023-05-12 16:35   ` Z572

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=875y91o7k7.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-sysadmin@gnu.org \
    --cc=mail@cbaines.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.