On Sat Nov 22, 2025 at 10:47 AM CET, Matthias Klose wrote: > Control: tags -1 + moreinfo > > please could you provide a self-contained test case, without any > references to a repo?
I don't know how to do that? I have no idea *why* it fails with rk3328 and rk3399, while it succeeds with rk3568 and rk3588. I'm not aware of that (same) issue happening elsewhere. I do know I can easily and consistently reproduce it. I (git) bisected the problem to this commit: https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/6c2e5bf68955 6c2e5bf68955 ("feat(build): use clang as a linker") But that's (pretty much) the extend to which I can narrow down the problem space. I don't understand what the changes in that commit would or could have as effect on gcc or ld. My knowledge wrt Makefiles is also limited. > also the error message more likely points to a linker error. I agree. > does it still build without lto enabled? I build it as follows, which IIUC disables LTO: ``` export ENABLE_LTO=0 export CROSS_COMPILE=aarch64-linux-gnu- make distclean make PLAT=rk3328 all ``` And it still fails with the same error. It's unfortunate that the above referenced commit also contains unrelated (AFAIK) changes, but I did learn that LTO is disabled by default. So I did another build with ``export ENABLE_LTO=1`` but that failed with the same error as well. So it appears LTO has no effect on this issue.
signature.asc
Description: PGP signature
