From: Max Brieiev <max.brieiev@gmail.com>
To: Akira Kyle <akira@akirakyle.com>
Cc: guix-devel@gnu.org
Subject: Re: Building arm64 guix system image
Date: Sun, 19 Feb 2023 14:18:55 +0200 [thread overview]
Message-ID: <86a619rgpc.fsf@gmail.com> (raw)
In-Reply-To: <87wn4gi3f9.fsf@akirakyle.com> (Akira Kyle's message of "Fri, 17 Feb 2023 10:36:20 -0700")
Hi,
Akira Kyle <akira@akirakyle.com> writes:
> I think I may be one of the few (only?) guix users that has a setup
> like this. IIRC getting grub setup with qemu was the one trickier
> parts of this. Feel free to ping me directly if you're having trouble.
Thanks.
> This is also how I got my guix system on qemu setup. For the record, I
> initially tried fedora but iirc, selinux was causing some
> difficulties.
Was it by any chance a syslinux? It causes build failures for me right
now. How did you work around it?
> This is the relevant issue
> https://issues.guix.gnu.org/60719. Unfortunately until this is fixed,
> guix system won't build since grub-efi depends on qemu-minimial which
> in turn (recently) depends on openbios-qemu-ppc.
I used time-machine to go back to the parent of "Unbundle OpenBIOS"
commit. open-bios-qemu-ppc issue is gone, but now it fails to build
syslinux:
guix time-machine --commit=53a1fce25a -- system image --system=aarch64-linux -t qcow2 ~/code/guix/gnu/system/examples/bare-bones.tmpl
...
building /gnu/store/gf432a4p1a3ll314g8sina9d4mis37ca-syslinux-6.04-pre-1.bb41e93.drv...
- 'build' phasebuilder for `/gnu/store/gf432a4p1a3ll314g8sina9d4mis37ca-syslinux-6.04-pre-1.bb41e93.drv' failed with exit code 1
build of /gnu/store/gf432a4p1a3ll314g8sina9d4mis37ca-syslinux-6.04-pre-1.bb41e93.drv failed
View build log at '/var/log/guix/drvs/gf/432a4p1a3ll314g8sina9d4mis37ca-syslinux-6.04-pre-1.bb41e93.drv.gz'.
cannot build derivation `/gnu/store/0smy079q2zsmnq0lvxw7c0amy9va3vv7-ipxe-qemu-1.21.1.drv': 1 dependencies couldn't be built
building /gnu/store/i7ir5yv7ifw1rh8x20141dx4c8h7wcgd-u-boot-2022.10.tar.xz.drv...
cannot build derivation `/gnu/store/rz143y972xmgv2gzw830b3ckm93z15l3-qemu-minimal-7.2.0.drv': 1 dependencies couldn't be built
guix system: error: build of `/gnu/store/rz143y972xmgv2gzw830b3ckm93z15l3-qemu-minimal-7.2.0.drv' failed
How can I proceed from here?
Thank you.
next prev parent reply other threads:[~2023-02-19 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 8:29 Building arm64 guix system image Max Brieiev
2023-02-17 17:36 ` Akira Kyle
2023-02-19 12:18 ` Max Brieiev [this message]
2023-02-19 12:51 ` Roman Scherer
2023-02-20 9:08 ` Error booting aarch64 installation image (was: Building arm64 guix system image) Max Brieiev
2023-02-20 10:03 ` Roman Scherer
2023-02-21 8:06 ` Error booting aarch64 installation image Max Brieiev
2023-02-22 10:56 ` Efraim Flashner
2023-02-19 20:01 ` Building arm64 guix system image Efraim Flashner
2023-02-20 10:31 ` Roman Scherer
2023-02-20 14:17 ` Efraim Flashner
2023-02-21 5:02 ` Andrew Patterson
2023-02-22 10:45 ` Efraim Flashner
2023-02-25 11:27 ` Roman Scherer
2023-02-23 18:41 ` Roman Scherer
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=86a619rgpc.fsf@gmail.com \
--to=max.brieiev@gmail.com \
--cc=akira@akirakyle.com \
--cc=guix-devel@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).