all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dftxbs3e <dftxbs3e@free.fr>
To: Guix Devel <guix-devel@gnu.org>
Subject: GNU Guix ported to powerp64-linux-gnu
Date: Sun, 23 Feb 2020 20:37:18 +0100	[thread overview]
Message-ID: <77bae158-f299-4866-c68a-44597c1b78f8@free.fr> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]

Hello!

Finally it succeeded. Thanks to everyone who has answered my countless
questions on the mailing list and IRC!

GNU Hello - /gnu/store/98wc63drnc5iwkcclls91iz181mmiv7c-hello-2.10
(natively built with: ./pre-inst-env guix build hello)

I used Gentoo (https://wiki.gentoo.org/wiki/Handbook:PPC64) as a base
PowerPC 64-bit big endian system. (precisely IBM POWER9)

source:

https://gitlab.com/lle-bout/guix - commit
f47e761a10675b05b07107035d5024618267a3ad (current master at time of writing)

bootstrap binaries:

https://gitlab.com/lle-bout/guix-bootstrap - commit
b017c0459bc65a53203eb056998be8abd7778e4a (current master at time of
writing) - currently it's unclear from which revision the bootstrap
binaries come from, a rebuild of all the binaries from the latest ported
guix's revision is pending.

How to build bootstrap binaries:

On a system where GNU Guix already works:

./pre-inst-env guix build --target=powerpc64-linux-gnu bootstrap-tarballs

Next steps are getting things to work on powerpc64le-linux-gnu (shouldnt
be too hard now) then rebase everything onto core-updates!

Leo



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2020-02-23 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 19:37 dftxbs3e [this message]
2020-02-24 15:18 ` GNU Guix ported to powerp64-linux-gnu Joshua Branson
2020-02-24 21:49   ` dftxbs3e
2020-03-08 20:56 ` 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

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

  git send-email \
    --in-reply-to=77bae158-f299-4866-c68a-44597c1b78f8@free.fr \
    --to=dftxbs3e@free.fr \
    --cc=guix-devel@gnu.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 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.