Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1271140 > unrolled thread

Bug#1118651: cpp-15-aarch64-linux-gnu: Build failure of TF-A for rk3328/rk3399 since TF-A commit 6c2e5bf68955

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1118651: cpp-15-aarch64-linux-gnu: Build failure of TF-A for rk3328/rk3399 since TF-A commit 6c2e5bf68955 Matthias Klose <doko@debian.org> - 2025-11-22 10:50 +0100
    Bug#1118651: cpp-15-aarch64-linux-gnu: Build failure of TF-A for rk3328/rk3399 since TF-A commit 6c2e5bf68955 "Diederik de Haas" <didi.debian@cknow.org> - 2025-11-22 21:00 +0100

#1271140 — Bug#1118651: cpp-15-aarch64-linux-gnu: Build failure of TF-A for rk3328/rk3399 since TF-A commit 6c2e5bf68955

Control: tags -1 + moreinfo

please could you provide a self-contained test case, without any 
references to a repo?

also the error message more likely points to a linker error.

does it still build without lto enabled?

[toc] | [next] | [standalone]

#1271220

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web