This is an auto-filled bug because app-crypt/aescrypt calls cc 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 CC implementation (like clang) by setting the CC variable. So this issue has been reproduced by setting the CC variable to x86_64-pc-linux-gnu-gcc and by removing the /usr/bin/cc - /usr/bin/gcc binaries.
Created attachment 637436 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Peter Alfredsen <firstname.lastname@example.org>
AuthorDate: 2020-12-15 20:11:49 +0000
Commit: Joonas Niilola <email@example.com>
CommitDate: 2021-01-05 08:32:42 +0000
app-crypt/aescrypt: bump to 3.14
Package-Manager: Portage-3.0.12, Repoman-3.0.2
Signed-off-by: Peter Alfredsen <firstname.lastname@example.org>
Signed-off-by: Joonas Niilola <email@example.com>
app-crypt/aescrypt/Manifest | 1 +
app-crypt/aescrypt/aescrypt-3.14.ebuild | 69 ++++++++++++++++++++++
app-crypt/aescrypt/files/aescrypt-3.14-iconv.patch | 40 +++++++++++++
3 files changed, 110 insertions(+)