[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#74849] [PATCH 0/6] Update ARM Trusted Firmware.
From: |
Vagrant Cascadian |
Subject: |
[bug#74849] [PATCH 0/6] Update ARM Trusted Firmware. |
Date: |
Sun, 15 Dec 2024 00:36:33 -0800 |
On 2024-12-13, Herman Rimm wrote:
> I assume the change to GCC 14 caused arm-trusted-firmware-imx8mq to
> fail. The last patch makes it build again, with a commit (patch) from
> https://github.com/nxp-imx/imx-atf.git.
>
> I think we should verify that boards using arm-trusted-firmware-imx8mq
> would still boot, but there aren't any U-Boot packages that use it.
It is debateable weather arm-trusted-firmware-imx8mq will be useable;
the corresponding u-boot builds depend on binary blobs for DDR
training. It might be reasonable to remove the imx8mq
arm-trusted-firmware variant entirely.
With this patch series applied (and with the guix-name patch reverted),
I have been unable to build arm-trusted-firmware for rk3328, rk3399,
imx8mq, or sun50i-a64. They all fail with similar errors:
starting phase `build'
MD
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/libfdt
MD
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/lib
MD
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/libc
Building rk3328
MD
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/bl31
MD
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/bl31/bl31
CC lib/libfdt/fdt.c
CC lib/libfdt/fdt_addresses.c
make: aarch64-none-elf-gcc: No such file or directory
make: *** [lib/libfdt/libfdt.mk:23:
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/libfdt/fdt.o]
Error 127
make: *** Waiting for unfinished jobs....
make: aarch64-none-elf-gcc: No such file or directory
make: *** [lib/libfdt/libfdt.mk:23:
/tmp/guix-build-arm-trusted-firmware-rk3328-2.12.drv-0/source/build/rk3328/debug/libfdt/fdt_addresses.o]
Error 127
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("-j" "6" "PLAT=rk3328"
"DEBUG=1") exit-status: 2 term-signal: #f stop-signal: #f>
phase `build' failed after 1.3 seconds
command "make" "-j" "6" "PLAT=rk3328" "DEBUG=1" failed with status 2
build process 8 exited with status 256
builder for
`/gnu/store/yx31pv6xahz3q74h9dirnyrf31446cpl-arm-trusted-firmware-rk3328-2.12.drv'
failed with exit code 1
build of
/gnu/store/yx31pv6xahz3q74h9dirnyrf31446cpl-arm-trusted-firmware-rk3328-2.12.drv
failed
I am guessing something broke native building, and people have only been
testing cross-building? Though they still build correctly on the older
arm-trusted-firmware on master.
live well,
vagrant
signature.asc
Description: PGP signature
- [bug#74849] [PATCH 4/6] gnu: make-arm-trusted-firmware: Use guix-name., (continued)
- [bug#74849] [PATCH 5/6] gnu: make-arm-trusted-firmware: Update to 2.12., Herman Rimm, 2024/12/13
- [bug#74849] [PATCH 3/6] import: utils: Move guix-name to (guix utils)., Herman Rimm, 2024/12/13
- [bug#74849] [PATCH 2/6] gnu: arm-trusted-firmware: Reformat., Herman Rimm, 2024/12/13
- [bug#74849] [PATCH 6/6] gnu: arm-trusted-firmware-imx8mq: Fix build., Herman Rimm, 2024/12/13
- [bug#74849] [PATCH 1/6] gnu: arm-trusted-firmware-rk3399: Reformat., Herman Rimm, 2024/12/13
- [bug#74849] [PATCH 0/6] Update ARM Trusted Firmware.,
Vagrant Cascadian <=
- [bug#74849] [PATCH v2 0/6] Update ARM Trusted Firmware., Herman Rimm, 2024/12/19
- [bug#74849] [PATCH v2 5/6] gnu: make-arm-trusted-firmware: Update to 2.12., Herman Rimm, 2024/12/19
- [bug#74849] [PATCH v2 3/6] import: utils: Move guix-name to (guix utils)., Herman Rimm, 2024/12/19