Re: The current state of Aarch64 on Guix

2017-07-24 Thread Ludovic Courtès
Hello Efraim, Efraim Flashner skribis: > I couldn't get haunt to find commonmark, so I'm just attaching what I've > written and formatted. Not sure why that happened. At worst, you can always run “guix build -f guix.scm” from the website/ directory of a guix-artwork.git checkout. Anyway, I’ve

Re: The current state of Aarch64 on Guix

2017-07-21 Thread Efraim Flashner
On Sat, Jul 01, 2017 at 05:44:12PM +0200, Ludovic Courtès wrote: > Hi Efraim, > > Efraim Flashner skribis: > > > 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. > > Excel

Re: The current state of Aarch64 on Guix

2017-07-02 Thread Leo Famulari
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 m

Re: The current state of Aarch64 on Guix

2017-07-01 Thread Ludovic Courtès
Hi Efraim, Efraim Flashner skribis: > 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. Excellent work! It looks like you’ve done your best without becoming yourself “upstream

Re: The current state of Aarch64 on Guix

2017-06-30 Thread Ricardo Wurmus
Efraim Flashner writes: > Currently Aarch64 support in guix is pretty good, as long as you don't > mind compiling for yourself :). […] > 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 o