From: Akira Kyle <akira@akirakyle.com>
To: 60719@debbugs.gnu.org
Cc: openbios@openbios.org, qemu-ppc@nongnu.org,
Marius Bakke <marius@gnu.org>
Subject: bug#60719: openbios-qemu-ppc fails to build on aarch64
Date: Sun, 29 Jan 2023 17:52:23 -0700 [thread overview]
Message-ID: <87cz6wx2rc.fsf@akirakyle.com> (raw)
In-Reply-To: <87wn5uhu31.fsf@gmail.com>
Andrew Patterson wrote on 17 Jan 06:16 +0100:
> I've submitted an issue to upstream:
> https://github.com/openbios/openbios/issues/11
It looks like from the other open issues, that the openbios team doesn't actually use the github issue tracker but their own mailing list, which I'm CC'ing, along with the qemu-ppc mailing list.
For anyone following this issue who wants to work around it and be able to `guix system reconfigure` on aarch64, I've copied the qemu package definition from before Marius unbundled a bunch of the qemu firmware, including openbios, to here:
https://github.com/akirakyle/guix-channel/blob/master/akira/qemu.scm
The relevant parts of my system config are then
(use-modules (akira qemu))
(define %qemu-package-replacements
`((,qemu-minimal . ,my-qemu-minimal)))
(define with-my-qemu
(package-input-rewriting %qemu-package-replacements))
(define my-grub-efi
(with-my-qemu grub-efi))
(define my-grub-efi-bootloader
(bootloader
(inherit grub-efi-bootloader)
(package my-grub-efi)))
(operating-system
...
(bootloader (bootloader-configuration
(bootloader my-grub-efi-bootloader)
(targets '("/boot"))
(keyboard-layout keyboard-layout)))
...)
prev parent reply other threads:[~2023-01-30 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 22:35 bug#60719: openbios-qemu-ppc fails to build on aarch64 Andrew Patterson
[not found] ` <handler.60719.B.167339174924378.ack@debbugs.gnu.org>
2023-01-17 4:12 ` bug#60719: Acknowledgement (openbios-qemu-ppc fails to build on aarch64) Andrew Patterson
2023-01-17 5:16 ` Andrew Patterson
2023-02-21 5:08 ` Andrew Patterson
2023-01-30 0:52 ` Akira Kyle [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz6wx2rc.fsf@akirakyle.com \
--to=akira@akirakyle.com \
--cc=60719@debbugs.gnu.org \
--cc=marius@gnu.org \
--cc=openbios@openbios.org \
--cc=qemu-ppc@nongnu.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.