unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: Jookia <166291@gmail.com>, 22384-done@debbugs.gnu.org
Subject: bug#22384: Requirements for an ARM port?
Date: Wed, 17 Jan 2018 15:02:40 +0100	[thread overview]
Message-ID: <87d12860sf.fsf@gnu.org> (raw)
In-Reply-To: <877esjf49p.fsf@gnu.org> (Mathieu Lirzin's message of "Mon, 15 Jan 2018 17:58:10 +0100")

Hello,

Mathieu Lirzin <mthl@gnu.org> skribis:

> Jookia <166291@gmail.com> writes:
>
>> I'm considering seeing if I can get GuixSD to work on an ARM board of mine. I'd
>> like to know what the main blockers are that I'll need to pass. From what I've
>> read and understood, the reason there's no ARM port now is lack of work and
>> reliance on GRUB. Assuming I bootstrap and set up a u-boot package for my
>> specific board, what else would I need to do?
>
> According to [1] Guix 0.14 provides support for ARMv7.  So I would
> consider this bug fixed.
>
> [1] https://www.gnu.org/software/guix/blog/2017/porting-guixsd-to-armv7/

Indeed.  As the post mentions, GuixSD has not been “ported to ARM” but
rather ported to a specific ARM board—but that’s the way it is.

Thanks for going through the bug backlog!

Ludo’.

      reply	other threads:[~2018-01-17 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 10:27 bug#22384: Requirements for an ARM port? Jookia
2016-01-17  8:10 ` Efraim Flashner
2016-01-17 20:39 ` Ludovic Courtès
2016-01-17 21:01   ` Jookia
2016-01-18  8:03     ` Ludovic Courtès
2018-01-15 16:58 ` Mathieu Lirzin
2018-01-17 14:02   ` Ludovic Courtès [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=87d12860sf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=166291@gmail.com \
    --cc=22384-done@debbugs.gnu.org \
    --cc=mthl@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).