From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Benjamin Slade <beoram@gmail.com>
Subject: Re: Guix on aarch64
Date: Sun, 26 Aug 2018 14:59:22 -0400 [thread overview]
Message-ID: <20180826185922.GB18912@jasmine.lan> (raw)
In-Reply-To: <87efelw1fr.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
On Sun, Aug 26, 2018 at 12:13:44PM -0400, Mark H Weaver wrote:
> Regardless, I think we should seriously consider moving the Aarch64
> build slave(s) to Hydra for now, until Cuirass is more mature.
I agree with your points about why berlin.guixsd.org makes it harder to
maintain the aarch64 port. I use Berlin substitutes alongside those of
Hydra but I don't actually do any build debugging with Berlin yet
because I don't know how to use the interface effectively.
Would it make any sense to split the two aarch64 machines up; one for
Hydra, one for Berlin?
It would be really great to get another pair of machines with similar
capabilities.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-26 19:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mutm72n7.fsf@jnanam.net>
[not found] ` <878t565k85.fsf@lassieur.org>
[not found] ` <87k1oq6wgf.fsf@jnanam.net>
2018-08-23 4:58 ` Guix on aarch64 Mark H Weaver
2018-08-23 16:09 ` Benjamin Slade
2018-08-24 10:32 ` Ludovic Courtès
2018-08-24 19:18 ` Ricardo Wurmus
2018-08-26 16:13 ` Mark H Weaver
2018-08-26 18:59 ` Leo Famulari [this message]
2018-08-27 8:04 ` Ricardo Wurmus
2018-08-27 18:54 ` Mark H Weaver
2018-08-27 19:11 ` Mark H Weaver
2018-08-27 19:26 ` Ricardo Wurmus
2018-08-27 21:05 ` Mark H Weaver
2018-08-27 21:56 ` Mark H Weaver
2018-08-28 5:39 ` Mark H Weaver
2018-08-28 7:57 ` Ricardo Wurmus
2018-08-28 10:00 ` Andreas Enge
2018-08-28 15:40 ` Mark H Weaver
2018-08-28 19:09 ` Leo Famulari
2018-08-28 19:22 ` Mark H Weaver
2018-08-27 19:50 ` Leo Famulari
2018-08-27 20:37 ` Ricardo Wurmus
2018-08-29 20:52 ` Joshua Branson
2018-08-30 20:47 ` Ricardo Wurmus
2018-08-30 9:49 ` Ludovic Courtès
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=20180826185922.GB18912@jasmine.lan \
--to=leo@famulari.name \
--cc=beoram@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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).