unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dftxbs3e <dftxbs3e@free.fr>
To: Chris Marusich <cmmarusich@gmail.com>,
	Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: New POWER9 machines for the Guix build farm?
Date: Mon, 9 Dec 2019 02:22:22 +0100	[thread overview]
Message-ID: <ddf9ccca-d389-eb29-e857-116066196c98@free.fr> (raw)
In-Reply-To: <87o8wipcz4.fsf@gmail.com>

On 12/9/19 1:19 AM, Chris Marusich wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>
>> Fellow Guix,
>>
>> The Guix sysadmins are considering buying shiny hardware for the
>> ci.guix.gnu.org build farm, and it would be awesome if that included
>> our first POWER9 machine(s)!
>>
>> However, few (if any) Guixers have any hands-on experience with this
>> architecture, let alone buying and installing whole systems. Some
>> remember a bad experience with a prominent vendor, and it would appear
>> that they're not alone[0].
>>
>> There's also some concern that getting these machines up and running
>> will take significant effort.
>>
>> So please, share your expertise and experience in this area! Ideally,
>> we need someone to volunteer to (help) set up any new POWER9 boxes and
>> later take care of them when needed.  It would certainly help justify
>> the multi-thousand-euro bill.
>>
>> Kind regards,
>>
>> T G-R
>>
>> PS: For the shorter term, I've applied for an 8-core POWER9 LE
>> instance (with 16 GiB of RAM) for Guix at OSUOSL[1].  Assuming that
>> it's accepted, it should be available within a week.
>>
>> [0]:
>> https://drewdevault.com/2019/09/23/RaptorCS-Blackbird-a-horror-story.html,
>> but read https://drewdevault.com/2019/10/10/RaptorCS-redemption.html
>> as well :-)
>> [1]: https://osuosl.org/services/powerdev/
> I think it's a great idea.  To test the waters, someone could try using
> one of these free VMs and see how Guix System does on them:
>
> https://openpowerfoundation.org/minicloud-free-openpower-cloud/
>
> First, bootstrap binaries have to be built for the hardware, anyway,
> right?  Maybe someone can do that work on one of those free VMs?
>
That work is already done!

See: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38459

Current issue is gcc-cross-boot0 not building.

See build log at: https://gitlab.com/lle-bout/guix/-/jobs/372934160

  reply	other threads:[~2019-12-09  1:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  0:50 New POWER9 machines for the Guix build farm? Tobias Geerinckx-Rice
2019-11-28  4:01 ` Brett Gilio
2019-11-28 10:57 ` Jonathan Brielmaier
2019-11-28 16:52   ` Leo Famulari
2019-11-29  8:25 ` dftxbs3e
2019-11-29 12:50   ` Marco van Hulten
2019-12-01 20:35     ` dftxbs3e
2019-12-09  0:19 ` Chris Marusich
2019-12-09  1:22   ` dftxbs3e [this message]
2019-12-13 18:55 ` Fwd: GNU Guix POWER9 OpenStack application (was: New POWER9 machines for the Guix build farm?) Tobias Geerinckx-Rice

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=ddf9ccca-d389-eb29-e857-116066196c98@free.fr \
    --to=dftxbs3e@free.fr \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).