unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 26714@debbugs.gnu.org
Subject: bug#26714: non-intel systems should use grub-efi
Date: Sun, 30 Apr 2017 12:57:28 -0700	[thread overview]
Message-ID: <87r309fz2v.fsf@gmail.com> (raw)
In-Reply-To: <20170430071407.GE28578@macbook42.flashner.co.il> (Efraim Flashner's message of "Sun, 30 Apr 2017 10:14:07 +0300")

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

Efraim Flashner <efraim@flashner.co.il> writes:

> I'm starting to stumble my way through building an install image for
> aarch64, and I changed gnu/system/install.scm to use 'grub-efi' in place
> of 'grub' in the list of packages (~line 333). Grub-efi builds
> successfully on armhf and aarch64 and grub does not, and as part of
> compiling install.scm grub is built as part of assembling the image.
>
> guix size grub:     157.5 MiB
> guix size grub-efi: 160.5 MiB
>
> I don't know a lot of how the install image is put together, or if using
> grub-efi in place of grub for building the image would be a problem for
> non-efi machines, but for non-intel machines at least we should use
> grub-efi for the grub calls.

Do the system installation tests pass with that change?  You can run the
following to find out:

  make check-system

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-04-30 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30  7:14 bug#26714: non-intel systems should use grub-efi Efraim Flashner
2017-04-30 14:10 ` Marius Bakke
2017-04-30 16:20   ` Efraim Flashner
2017-04-30 19:57 ` Chris Marusich [this message]
2020-04-07 14:54 ` Marius Bakke

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=87r309fz2v.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=26714@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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).