GNU bug report logs - #78251
arm-trusted-firmware for pine64 FTBFS

Previous Next

Full log

View this message in rfc822 format

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Efraim Flashner <efraim <at> flashner.co.il>, 78251 <at> debbugs.gnu.org
Cc: gabriel <at> erlikon.ch, efraim <at> flashner.co.il
Subject: bug#78251: arm-trusted-firmware for pine64 FTBFS
Date: Mon, 05 May 2025 10:43:28 -0700

[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)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.