From: Vagrant Cascadian <vagrant@debian.org>
To: Roman Scherer <roman@burningswell.com>
Cc: 74710@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#74710] [PATCH] gnu: ipxe: Update to 24db39fb2983ca83ab5c6ee37cb57a4f7f6f94e6.
Date: Fri, 06 Dec 2024 13:05:39 -0800 [thread overview]
Message-ID: <87ed2kv7x8.fsf@wireframe> (raw)
In-Reply-To: <87ldwsvahz.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On 2024-12-06, Vagrant Cascadian wrote:
> On 2024-12-06, Roman Scherer wrote:
>> * gnu/packages/bootloaders.scm (ipxe): Update to 24db39fb2983ca83ab5c6ee37cb57a4f7f6f94e6.
>
> This fails to build on aarch64-linux for me, with lots of "unrecognized
> command-line option" errors, such as:
...
> View build log at '/var/log/guix/drvs/s6/0h3s4h3rass2fq6sdkxgs9nf2nhbij-ipxe-1.21.1-3.24db39f.drv.gz'.
> guix build: error: build of `/gnu/store/s60h3s4h3rass2fq6sdkxgs9nf2nhbij-ipxe-1.21.1-3.24db39f.drv' failed
>
>
> Although I see the same build failures without the patch applied...
Ah, but it *does* fix building "ipxe-qemu"! So for that it would be nice
to apply the patch!
We should probably mark "ipxe" as x86_64-linux only; I think it is not
designed to build on other architectures.
That said, this does improve the situation for aarch64, triggering only
about 19 rebuilds... I have yet to finish testing how those rebuilds go,
but it is in progress.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-12-06 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:38 [bug#74710] [PATCH] gnu: ipxe: Update to 24db39fb2983ca83ab5c6ee37cb57a4f7f6f94e6 Roman Scherer
2024-12-06 20:10 ` Vagrant Cascadian
2024-12-06 21:05 ` Vagrant Cascadian [this message]
2024-12-07 8:23 ` bug#74710: " Vagrant Cascadian
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=87ed2kv7x8.fsf@wireframe \
--to=vagrant@debian.org \
--cc=74710@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=roman@burningswell.com \
/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).