GNU bug report logs -
#78251
arm-trusted-firmware for pine64 FTBFS
Previous Next
To reply to this bug, email your comments to 78251 AT debbugs.gnu.org.
There is no need to reopen the bug first.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
efraim <at> flashner.co.il, gabriel <at> erlikon.ch, vagrant <at> debian.org, bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Mon, 05 May 2025 06:29:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Efraim Flashner <efraim <at> flashner.co.il>:
New bug report received and forwarded. Copy sent to
efraim <at> flashner.co.il, gabriel <at> erlikon.ch, vagrant <at> debian.org, bug-guix <at> gnu.org.
(Mon, 05 May 2025 06:29:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I was trying to deploy a new generation on my pine64 and the
arm-trusted-firmware failed to build. I tried changing the make-flags
on arm-trusted-firmware to set CFLAGS=-Os but the overflow was still 216
bytes. Changing it to -O2 made it 4312 bytes. Adding DEBUG=0 didn't
make a difference either.
Excerpt from the build log:
AS plat/common/aarch64/platform_mp_stack.S
PP bl31/bl31.ld.S
AR /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/lib/libfdt.a
AR /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/lib/libc.a
LD /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf
ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
ld: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.rela.dyn' will not fit in region `RAM'
ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
ld: BL31 image has exceeded its limit.
ld: region `RAM' overflowed by 216 bytes
collect2: error: ld returned 1 exit status
make: *** [Makefile:1557: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf] Error 1
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("-j" "4" "PLAT=sun50i_a64" "DEBUG=0" "CC=gcc" "DEBUG=1") exit-status: 2 term-signal: #f stop-signal: #f>
phase `build' failed after 4.6 seconds
command "make" "-j" "4" "PLAT=sun50i_a64" "DEBUG=0" "CC=gcc" "DEBUG=1" failed with status 2
build process 6 exited with status 256
builder for `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed with exit code 1
@ build-failed /gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv - 1 builder for `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed with exit code 1
derivation '/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' offloaded to 'ubuntu.unicorn-typhon.ts.net' failed: build of `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed
build of /gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv failed
View build log at '/var/log/guix/drvs/9d/5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv'.
guix build: error: build of `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed
--
Efraim Flashner <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Mon, 05 May 2025 16:57:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 78251 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2025-05-05, Efraim Flashner wrote:
> I was trying to deploy a new generation on my pine64 and the
> arm-trusted-firmware failed to build. I tried changing the make-flags
> on arm-trusted-firmware to set CFLAGS=-Os but the overflow was still 216
> bytes. Changing it to -O2 made it 4312 bytes. Adding DEBUG=0 didn't
> make a difference either.
>
>
> Excerpt from the build log:
>
> AS plat/common/aarch64/platform_mp_stack.S
> PP bl31/bl31.ld.S
> AR /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/lib/libfdt.a
> AR /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/lib/libc.a
> LD /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf
> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
> ld: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.rela.dyn' will not fit in region `RAM'
> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
> ld: BL31 image has exceeded its limit.
> ld: region `RAM' overflowed by 216 bytes
> collect2: error: ld returned 1 exit status
> make: *** [Makefile:1557: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf] Error 1
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "make" arguments: ("-j" "4" "PLAT=sun50i_a64" "DEBUG=0" "CC=gcc" "DEBUG=1") exit-status: 2 term-signal: #f stop-signal: #f>
> phase `build' failed after 4.6 seconds
> command "make" "-j" "4" "PLAT=sun50i_a64" "DEBUG=0" "CC=gcc" "DEBUG=1" failed with status 2
> build process 6 exited with status 256
> builder for `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed with exit code 1
> @ build-failed /gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv - 1 builder for `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed with exit code 1
> derivation '/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' offloaded to 'ubuntu.unicorn-typhon.ts.net' failed: build of `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed
> build of /gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv failed
> View build log at '/var/log/guix/drvs/9d/5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv'.
> guix build: error: build of `/gnu/store/9d5f5yaqsiagglzlhwak0ywwlv7gfji0-arm-trusted-firmware-sun50i-a64-2.12.1.drv' failed
It also fails to buidl for me on a mnt/reform2 rk3588 running guix
system on aarch64-linux ... Interestingly, it appears to cross-build for
x86_64-linux just fine ...
I do not see any immediately obvious toolchain changes at a cursory
glance...
Might be worth bisecting to see where it started failing (presuming it
ever built natively)? I might give that a whirl...
There is also a 2.12.2 version available now; might be worth updating
just to see if it fixes it...
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Mon, 05 May 2025 17:03:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 78251 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2025-05-05, Vagrant Cascadian wrote:
> On 2025-05-05, Efraim Flashner wrote:
>> I was trying to deploy a new generation on my pine64 and the
>> arm-trusted-firmware failed to build. I tried changing the make-flags
>> on arm-trusted-firmware to set CFLAGS=-Os but the overflow was still 216
>> bytes. Changing it to -O2 made it 4312 bytes. Adding DEBUG=0 didn't
>> make a difference either.
...
>> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
>> ld: BL31 image has exceeded its limit.
>> ld: region `RAM' overflowed by 216 bytes
>> collect2: error: ld returned 1 exit status
>> make: *** [Makefile:1557: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf] Error 1
...
> There is also a 2.12.2 version available now; might be worth updating
> just to see if it fixes it...
Tested 2.12.2, same problem, but at least all the other targets still
build successfully... :/
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Mon, 05 May 2025 17:44:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 78251 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2025-05-05, Vagrant Cascadian wrote:
> On 2025-05-05, Efraim Flashner wrote:
>> I was trying to deploy a new generation on my pine64 and the
>> arm-trusted-firmware failed to build. I tried changing the make-flags
>> on arm-trusted-firmware to set CFLAGS=-Os but the overflow was still 216
>> bytes. Changing it to -O2 made it 4312 bytes. Adding DEBUG=0 didn't
>> make a difference either.
...
>> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
>> ld: BL31 image has exceeded its limit.
>> ld: region `RAM' overflowed by 216 bytes
>> collect2: error: ld returned 1 exit status
>> make: *** [Makefile:1557: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf] Error 1
...
> Might be worth bisecting to see where it started failing (presuming it
> ever built natively)? I might give that a whirl...
Well, the issue was introduced in the commit where 2.12.1 was added,
3aed6ee07bd0d22cd6cf897eada7ea3b95f6adf5, the immediately preceeding
commit still built successfully.
So one option might be to revert to 2.12 for sun50i-a64 ... but
obviously a better option would be to fix it properly... :)
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Mon, 05 May 2025 18:00:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 78251 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2025-05-05, Vagrant Cascadian wrote:
> On 2025-05-05, Vagrant Cascadian wrote:
>> On 2025-05-05, Efraim Flashner wrote:
>>> I was trying to deploy a new generation on my pine64 and the
>>> arm-trusted-firmware failed to build. I tried changing the make-flags
>>> on arm-trusted-firmware to set CFLAGS=-Os but the overflow was still 216
>>> bytes. Changing it to -O2 made it 4312 bytes. Adding DEBUG=0 didn't
>>> make a difference either.
> ...
>>> ld: address 0x500d8 of /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf section `.data' is not within region `RAM'
>>> ld: BL31 image has exceeded its limit.
>>> ld: region `RAM' overflowed by 216 bytes
>>> collect2: error: ld returned 1 exit status
>>> make: *** [Makefile:1557: /tmp/guix-build-arm-trusted-firmware-sun50i-a64-2.12.1.drv-0/source/build/sun50i_a64/debug/bl31/bl31.elf] Error 1
> ...
>> Might be worth bisecting to see where it started failing (presuming it
>> ever built natively)? I might give that a whirl...
>
> Well, the issue was introduced in the commit where 2.12.1 was added,
> 3aed6ee07bd0d22cd6cf897eada7ea3b95f6adf5, the immediately preceeding
> commit still built successfully.
And bisected upstream with:
guix build --with-commit=arm-trusted-firmware-sun50i-a64=$(git show | awk '/^commit/{print $2}'}) arm-trusted-firmware-sun50i-a64
git bisect start
# status: waiting for both good and bad commits
# good: [4ec2948fe3f65dba2f19e691e702f7de2949179c] Merge "docs(changelog): changelog for v2.12 release" into integration
git bisect good 4ec2948fe3f65dba2f19e691e702f7de2949179c
# status: waiting for bad commit, 1 good commit known
# bad: [8cf9edba5cc3ec11ed5463f206aa5819f7fdbade] docs(changelog): changelog for lts-v2.12.1 release
git bisect bad 8cf9edba5cc3ec11ed5463f206aa5819f7fdbade
# good: [16b87247ed03fbe98c5c4a96c4dd00844ae53284] fix(security): add CVE-2024-7881 mitigation to Cortex-X3
git bisect good 16b87247ed03fbe98c5c4a96c4dd00844ae53284
# bad: [7e41b706e97c0e36e19d51b6a1785280e9ff4108] fix(cpus): workaround for Neoverse-N2 erratum 3701773
git bisect bad 7e41b706e97c0e36e19d51b6a1785280e9ff4108
# bad: [24526273fc504500c36029fa8c188f4e394f4f07] fix(cpus): workaround for Cortex-A720 erratum 3699561
git bisect bad 24526273fc504500c36029fa8c188f4e394f4f07
# bad: [7e4bf042a0dda901b9e5a7f79d37a34d81614e79] chore(cpus): fix incorrect header macro
git bisect bad 7e4bf042a0dda901b9e5a7f79d37a34d81614e79
# bad: [9427c061eb8dee00c32d72c20d6bc231002a575c] fix(security): apply SMCCC_ARCH_WORKAROUND_4 to affected cpus
git bisect bad 9427c061eb8dee00c32d72c20d6bc231002a575c
# good: [bea64fd5272deaf53111135baf36abb47b73b93e] fix(security): add support in cpu_ops for CVE-2024-7881
git bisect good bea64fd5272deaf53111135baf36abb47b73b93e
# first bad commit: [9427c061eb8dee00c32d72c20d6bc231002a575c] fix(security): apply SMCCC_ARCH_WORKAROUND_4 to affected cpus
Yay guix build --with-commit!!!!
Last time I built this version on Debian it worked fine ... but now you
have me wanting to double-check! Differences in the toolchains between
Debian and guix might be a clue...
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Mon, 05 May 2025 18:24:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 78251 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2025-05-05, Vagrant Cascadian wrote:
> Last time I built this version on Debian it worked fine ... but now you
> have me wanting to double-check! Differences in the toolchains between
> Debian and guix might be a clue...
Just checked again, and 2.12.1 still builds fine natively on
Debian... so that might be something worth exploring...
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#78251; Package
guix.
(Tue, 06 May 2025 12:28:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 78251 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Mon, May 05, 2025 at 11:23:25AM -0700, Vagrant Cascadian wrote:
> On 2025-05-05, Vagrant Cascadian wrote:
> > Last time I built this version on Debian it worked fine ... but now you
> > have me wanting to double-check! Differences in the toolchains between
> > Debian and guix might be a clue...
>
> Just checked again, and 2.12.1 still builds fine natively on
> Debian... so that might be something worth exploring...
Thanks for doing all this work so far! I assume Debian is using gcc-14
for the build. I don't see anything obvious in the debian/rules file¹
¹ https://sources.debian.org/src/arm-trusted-firmware/2.12.1%2Bdfsg-1/debian/rules/
--
Efraim Flashner <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
Reply sent
to
Efraim Flashner <efraim <at> flashner.co.il>:
You have taken responsibility.
(Tue, 06 May 2025 13:26:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Efraim Flashner <efraim <at> flashner.co.il>:
bug acknowledged by developer.
(Tue, 06 May 2025 13:26:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 78251-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Mon, May 05, 2025 at 11:23:25AM -0700, Vagrant Cascadian wrote:
> On 2025-05-05, Vagrant Cascadian wrote:
> > Last time I built this version on Debian it worked fine ... but now you
> > have me wanting to double-check! Differences in the toolchains between
> > Debian and guix might be a clue...
>
> Just checked again, and 2.12.1 still builds fine natively on
> Debian... so that might be something worth exploring...
>
> live well,
> vagrant
I've adjusted arm-trusted-firmware-sun50i-a64 to build with gcc-14.
gcc-13 and gcc-14 work, gcc-12 and gcc-11 don't.
--
Efraim Flashner <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 8 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.