This is an auto-filled bug because app-misc/lcdproc calls ar directly.
The issue was originally discovered on amd64, but it may be reproducible on other arches as well.
If you think that a different summary clarifies the issue better, feel free to change it.
Attached build log and emerge --info.
If you think it doesn't make sense fix these type of issues, I'd like to point out that won't be possible use a different AR implementation (like llvm-ar) by setting the AR variable. So this issue has been reproduced by setting the AR variable to x86_64-pc-linux-gnu-ar and by removing the /usr/bin/ar binary.
Created attachment 637876 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Conrad Kostecki <email@example.com>
AuthorDate: 2020-05-11 21:52:03 +0000
Commit: Conrad Kostecki <firstname.lastname@example.org>
CommitDate: 2020-05-11 21:53:54 +0000
app-misc/lcdproc: don't call directly ar
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Conrad Kostecki <email@example.com>
.../lcdproc-0.5.9-respect-users-ldflags.patch | 25 +++
app-misc/lcdproc/lcdproc-0.5.9-r1.ebuild | 233 +++++++++++++++++++++
2 files changed, 258 insertions(+)