From: Vagrant Cascadian <vagrant@debian.org>
To: Herman Rimm <herman@rimm.ee>, 74849@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#74849] [PATCH v2 0/6] Update ARM Trusted Firmware.
Date: Thu, 19 Dec 2024 15:18:51 -0800 [thread overview]
Message-ID: <87ttazuuqs.fsf@contorta> (raw)
In-Reply-To: <cover.1734645720.git.herman@rimm.ee>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On 2024-12-19, Herman Rimm wrote:
> This revision configures the ARM Trusted Firmware differently when doing
> a native build, which should fix the 'aarch64-none-elf-gcc' errors.
That does appear to work, nice!
I had another working patch that added to native inputs:
(cross-gcc "aarch64-none-elf")
(cross-binutils "aarch64-none-elf")
And passed CROSS_COMPILE=aarch64-none-elf- ...
But those extra inputs are silly and your fix is much nicer!
> I will give the guix-name procedure a more appropriate name in another
> patch (series).
Could the guix-name stuff just be submitted as it's own patch series?
It seems more-or-less unrelated to this patch series, only resulting in
a few small line changes...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-12-19 23:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 12:23 [bug#74849] [PATCH 0/6] Update ARM Trusted Firmware Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 1/6] gnu: arm-trusted-firmware-rk3399: Reformat Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 2/6] gnu: arm-trusted-firmware: Reformat Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 3/6] import: utils: Move guix-name to (guix utils) Herman Rimm via Guix-patches via
2024-12-17 13:52 ` Ludovic Courtès
2024-12-13 12:25 ` [bug#74849] [PATCH 4/6] gnu: make-arm-trusted-firmware: Use guix-name Herman Rimm via Guix-patches via
2024-12-15 8:04 ` Vagrant Cascadian
2024-12-15 23:05 ` Herman Rimm via Guix-patches via
2024-12-19 19:50 ` [bug#74849] fixed guix-name missing, but still fails on aarch64 Vagrant Cascadian
2024-12-13 12:25 ` [bug#74849] [PATCH 5/6] gnu: make-arm-trusted-firmware: Update to 2.12 Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 6/6] gnu: arm-trusted-firmware-imx8mq: Fix build Herman Rimm via Guix-patches via
2024-12-15 8:36 ` [bug#74849] [PATCH 0/6] Update ARM Trusted Firmware Vagrant Cascadian
2024-12-19 22:10 ` [bug#74849] [PATCH v2 " Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 1/6] gnu: arm-trusted-firmware-rk3399: Reformat Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 2/6] gnu: arm-trusted-firmware: Reformat Herman Rimm via Guix-patches via
2024-12-19 23:34 ` Vagrant Cascadian
2024-12-19 22:10 ` [bug#74849] [PATCH v2 3/6] import: utils: Move guix-name to (guix utils) Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 4/6] gnu: make-arm-trusted-firmware: Use guix-name Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 5/6] gnu: make-arm-trusted-firmware: Update to 2.12 Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 6/6] gnu: arm-trusted-firmware-imx8mq: Fix build Herman Rimm via Guix-patches via
2024-12-19 23:18 ` Vagrant Cascadian [this message]
2024-12-20 0:22 ` bug#74849: [PATCH v2 0/6] Update ARM Trusted Firmware 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=87ttazuuqs.fsf@contorta \
--to=vagrant@debian.org \
--cc=74849@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=herman@rimm.ee \
/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).