unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 宋文武 <iyzsong@envs.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 15:27:47 +0100	[thread overview]
Message-ID: <87mt2d3796.fsf@cbaines.net> (raw)
In-Reply-To: <87ednpy4c3.fsf@envs.net>

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]


宋文武 <iyzsong@envs.net> writes:

> Christopher Baines <mail@cbaines.net> writes:
>
>> This is a start, but more hardware will be needed to keep up with the
>> master branch, plus testing patches and other branches, so if you have
>> hardware to hand, or know of hardware available for purchase that might
>> be suitable, that would be really useful to know about.
>
> Hello I have a visionfive2 4GiB memory model with a nvme disk, does it
> suitable to join the guix build farm?  My home network is behind NAT.

Yes! At least in my opinion.

Ideally the build machines would be owned by guix-europe, but that's
something to look at sorting out once it's up and running.

The NAT is no problem, the build coordinator (intentionally) has very
few requirements.

The first hurdle to overcome is just getting the build coordinator agent
available on the system. For the board I have, I cross compiled the
guix-build-coordinator-agent-only package, then used guix archive to
copy it and all the dependencies across but any approach that works is
fine.

Once you've got that far, let me know and I can privately send you the
arguments to use when running the agent.

Thanks!

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2023-05-09 14:33 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 [this message]
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
2023-05-10  9:05 ` Andreas Enge
2023-05-10  9:24   ` Christopher Baines
2023-05-11 11:15 ` 郑俊杰
     [not found] ` <87mt298pm9.fsf@qq.com>
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mt2d3796.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=guix-sysadmin@gnu.org \
    --cc=iyzsong@envs.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).