all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zacchaeus Scheffer <zaccysc@gmail.com>
To: 49553@debbugs.gnu.org
Subject: bug#49553: ARM installation
Date: Tue, 13 Jul 2021 16:27:00 -0400	[thread overview]
Message-ID: <ae7d37d4-62be-f843-a6ea-f0b0f96e3a26@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]

Hi bug-guix,

I tried running:

guix system image --system=armhf-linux -e '((@ (gnu system install) os-with-u-boot) (@ (gnu system install) installation-os) "aoeuthant")'

And got two unexpected behaviors.

First of all, I get the error:

|builder for 
`/gnu/store/05njkp7140yzkik9c3r3imfj0jdj68k1-dhcp-4.4.2-P1.tar.xz.drv' 
failed with exit code 1
build of 
/gnu/store/05njkp7140yzkik9c3r3imfj0jdj68k1-dhcp-4.4.2-P1.tar.xz.drv failed
View build log at 
'/var/log/guix/drvs/05/njkp7140yzkik9c3r3imfj0jdj68k1-dhcp-4.4.2-P1.tar.xz.drv.bz2'.
cannot build derivation 
`/gnu/store/4nswzq8wdnj77z16v3gmjb2b31pphh7f-isc-dhcp-4.4.2-P1.drv': 1 
dependencies couldn't be built
guix system: error: build of 
`/gnu/store/4nswzq8wdnj77z16v3gmjb2b31pphh7f-isc-dhcp-4.4.2-P1.drv' failed

(log attached here)

According to 
https://guix.gnu.org/manual/en/html_node/Building-the-Installation-Image.html, 
specifying an invalid board (notice "aoeuthant" at the end of the 
command I tried) should print a list of possible boards.  A list of 
possible boards was NOT printed, though it is possible this was caused 
by the first error, though I would expect a list of boards before it 
tries to make the image.

-Zacchaeus


[-- Attachment #1.2: Type: text/html, Size: 2255 bytes --]

[-- Attachment #2: njkp7140yzkik9c3r3imfj0jdj68k1-dhcp-4.4.2-P1.tar.xz.drv.bz2 --]
[-- Type: application/octet-stream, Size: 240 bytes --]

                 reply	other threads:[~2021-07-13 20:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae7d37d4-62be-f843-a6ea-f0b0f96e3a26@gmail.com \
    --to=zaccysc@gmail.com \
    --cc=49553@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.