From mboxrd@z Thu Jan 1 00:00:00 1970 From: Efraim Flashner Subject: The current state of Aarch64 on Guix Date: Thu, 29 Jun 2017 21:37:58 +0300 Message-ID: <20170629183758.GD1734@macbook42.flashner.co.il> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="/3yNEOqWowh/8j+e" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQeKP-0008GR-GP for guix-devel@gnu.org; Thu, 29 Jun 2017 14:38:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQeKK-0002RG-KH for guix-devel@gnu.org; Thu, 29 Jun 2017 14:38:09 -0400 Received: from flashner.co.il ([178.62.234.194]:54639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQeKK-0002Qw-7x for guix-devel@gnu.org; Thu, 29 Jun 2017 14:38:04 -0400 Received: from localhost (85.64.232.168.dynamic.barak-online.net [85.64.232.168]) by flashner.co.il (Postfix) with ESMTPSA id CCFE340321 for ; Thu, 29 Jun 2017 18:38:02 +0000 (UTC) Content-Disposition: inline List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --/3yNEOqWowh/8j+e Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. General problem points/packages: * Java is currently out, sablevm-classpath doesn't compile, so currently there is no path for java. A quick check showed about 140 packages depend on sablevm-classpath. * Go: go-1.4.x doesn't support aarch64 (or mips). I have a patch against our gcc to build gccgo, and it produces a go binary, but it fails to actually build anything. When I checked Debian I saw they crosscompile their arm64 go binary from amd64. * ocaml-4.01.0: Doesn't build on aarch64, haven't investigated. * julia: aarch64 is officially supported, but it has only been tested on superpowerful boards, like the ThunderX. I haven't gotten it to build yet. * clisp: our current version doesn't build on aarch64, there isn't support yet. There are newer builds but no offical release yet, and I haven't tested those yet. * gprolog: No upstream support and AFAICT no one is working on it. * ldc: 1.x is supposed to support aarch64, 0.17.*, aka ldc-bootstrap, doesn't, it fails while compiling phobos, which has no aarch64 support in that version. * rust: Has upstream support, our package uses the i686 version as a bootstrap, so only i686 and x86_64 have support in guix ATM. * haskell: There is no upstream aarch64 binary to use for bootstrapping. I'm thinking of trying to use qemu-system-x86_64 as the shell and emulate x86_64 on my aarch64 board to cross-compile it to aarch64. * 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, I haven't tried to fix it. * kernel: I don't know if there's a generic armv8 kernel config It sounds like its all doom and gloom, but its not too bad. `guix package -A | wc -l' shows me 5341 (5208 without sablevm-classpath), compared with ~5600 on x86_64. --=20 Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7=9D = =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted --/3yNEOqWowh/8j+e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAllVSMwACgkQQarn3Mo9 g1HbAA//R08yAfBRFGrwgxy20yhxrrCmGa4DO7HgmfVabMYlTzVmD9tEbfxhCsWO veg77becei3iMHkYoLcs2pZUOl9+pmpSyAeu9iitLNk6boRLzHyqiZjMGtUG7SWD 7Uy/zOf1Wfzz+QAM0SBH9QuVBWHZFfOZG3pyUbdfGK4M09YbeIO+25l4mdMvlEdY YForI0NWT5E8Z2h/yQR8PiyYvxTYU113T1Zw7oGrZSVsTD1pKtz4xqXGTt3ZJTAY SW4MgiB8d1CvUZGoUfUa3Wnbh/0YU7Y1utJEuZLlo1szMNu9fiSKVj/HWd5SOdXK Ywic164ex+I3XgHWrzapLehgjvRumB9IFvbYdw7o0DxiZ6jFW4YeOtWDcl3eVVCb VpriA/O7Pw/D37lUwYUMO0/0yNq7byp6EjW/iPz6aAsc3LHZJjA7/nme3HtJuDnB EHBMEUBhIZUiGsZ3MIk+QAX/yYKPbCDQaRh9PsLHslN5I3GOy5k82NPFo0xvaVH3 2cZh31qdaZdhNe4pyH3pPqzrWX/euiC7RNy/eQ8j3IEJrLW1sxpf46BeXPkCgWBZ eZpXp3SqJm13fe1JCQOVcIFgknLXDRtJP3EtMDDikc7H9vBfN/0CMUpFia9NbLXB ra8kfjp5RDm4YAn862b8agPN4neRne36PDvyLgUmGnVSpGprpIs= =9Ots -----END PGP SIGNATURE----- --/3yNEOqWowh/8j+e--