From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: The current state of Aarch64 on Guix
Date: Sun, 2 Jul 2017 10:27:50 -0400 [thread overview]
Message-ID: <20170702142750.GA15315@jasmine.lan> (raw)
In-Reply-To: <20170629183758.GD1734@macbook42.flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Thu, Jun 29, 2017 at 09:37:58PM +0300, Efraim Flashner wrote:
> Currently Aarch64 support in guix is pretty good, as long as you don't
> mind compiling for yourself :). Potential downfalls are too little RAM
> (I limited my boards to 2GB minimum) and using an SD card. For building
> packages I made sure that between RAM and swap I have at least 6 GB,
> which I don't recall giving me any issues.
>
> There were problems with actually building the guix binary in time for
> the 0.13 release, it has since been fixed and I have an unoffical
> aarch64 binary install tarball at flashner.co.il/~efraim/. Also there is
> the signing key for my odroid running guix-publish. The url for the
> guix-publish server is git.flashner.co.il:8181.
Awesome! I'm looking forward to getting some aarch64 hardware for Guix.
> General problem points/packages:
[...]
> * qt-4: does not build, I've hardly put any time into it.
> * gnucash: The ancient webkit version they use didn't build on aarch64,
Qt 4 and that old version of webkit are unmaintained, full of bugs, and
we will probably have to remove them soon, regardless of whether or not
something depends on them. So I don't think you should worry about
trying to build them for aarch64.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-07-02 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 18:37 The current state of Aarch64 on Guix Efraim Flashner
2017-06-30 19:26 ` Ricardo Wurmus
2017-07-01 15:44 ` Ludovic Courtès
2017-07-21 15:05 ` Efraim Flashner
2017-07-24 13:39 ` Ludovic Courtès
2017-07-02 14:27 ` Leo Famulari [this message]
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=20170702142750.GA15315@jasmine.lan \
--to=leo@famulari.name \
--cc=efraim@flashner.co.il \
--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 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).