all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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] fixed guix-name missing, but still fails on aarch64
Date: Thu, 19 Dec 2024 11:50:15 -0800	[thread overview]
Message-ID: <87y10bv4eg.fsf@contorta> (raw)
In-Reply-To: <azztkffs63gez76tawkmb63m55cj6ficnipxxhyxbd7yda45wt@h72scnd3jbi6>

[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]

On 2024-12-16, Herman Rimm wrote:
> On Sun, Dec 15, 2024 at 12:04:06AM -0800, Vagrant Cascadian wrote:
>> On 2024-12-13, Herman Rimm wrote:
>> > * gnu/packages/firmware.scm (make-arm-trusted-firmware): Use guix-name.
>> > (arm-trusted-firmware-sun50i-a64): Return base package directly.
>> 
>> With this patch applied, I get:
>
> Is [PATCH 3/6] also applied?  What command do you use?

Apparently not, because I did not receive the patch!  I had noticed it
was missing, but misread your 0/6 comment about it...

Presumably etc/teams.scm did not include me in CC because it did not
match any of the file patterns I am on a team for... so I had to go
fishing in the bug tracker to get the full patch series. Kind of kills
most of the benefit of getting CCed on a patch series, in my opinion,
but that is outside the scope of this issue... :)

With 3/6 applied, it gets further... but still fails building on
aarch64-linux...


> Applying this patch series to 65892d9f20aa7a8649797507bb1ec867285083fb,
> creating a branch and setting up a channel for it, running this command
> on a x86_64 system succeeds:
>
> guix time-machine -C channels.scm -- build arm-trusted-firmware-rk3399

On aarch64-linux, with patches applied on top of
07b4b1d055c36c6c61d39273c26974771dbfe805, it still fails with errors
like this:

/gnu/store/d7q6yazfa1bxf4x7p9n3b99hn97q6bvw-bash-minimal-5.1.16/bin/sh: line 1: aarch64-none-elf-gcc: command not found
make: *** [lib/libfdt/libfdt.mk:23: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.drv-0/source/build/sun50i_a64/debug/libfdt/fdt_strerror.o] Error 127

Maybe it builds correctly on x86_64, but given that most targets are
aarch64 targets, it ought to be able to build natively too.

As mentioned earlier, I would guess this is either a bug in upstream, or
in the way guix is passing a cross-toolchain of some kind...


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2024-12-19 19:51 UTC|newest]

Thread overview: 25+ 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       ` Vagrant Cascadian [this message]
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-20 20:11       ` Herman Rimm via Guix-patches via
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-20 13:04     ` Nicolas Goaziou via Guix-patches via
2024-12-20 17:50       ` 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   ` [bug#74849] [PATCH v2 0/6] Update ARM Trusted Firmware Vagrant Cascadian
2024-12-20  0:22     ` bug#74849: " 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

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

  git send-email \
    --in-reply-to=87y10bv4eg.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 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.