This is an auto-filed bug because app-crypt/libu2f-host misses USE=static-libs and installs '.a' files. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. The issue was discovered on the version reported in the summary but it may be reproducible on other versions as well. The best solution is avoid to build the '.a' files by touching the configure. In case the buildsystem makes your life hard, a good compromise would be just remove the files. NOTE: If you want to change the summary, to avoid auto-filed duplicates, please at least keep the word 'static-libs'
See also: https://projects.gentoo.org/qa/policy-guide/installed-files.html#pg0302
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b0f7c53c0adbe7043f5c6b0a14d5bf10ba39b1dc commit b0f7c53c0adbe7043f5c6b0a14d5bf10ba39b1dc Author: Jakov Smolic <jakov.smolic@sartura.hr> AuthorDate: 2020-11-14 20:17:35 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2020-11-14 20:17:35 +0000 app-crypt/libu2f-host: disable static libs Closes: https://bugs.gentoo.org/725688 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Jakov Smolic <jakov.smolic@sartura.hr> Signed-off-by: David Seifert <soap@gentoo.org> app-crypt/libu2f-host/libu2f-host-1.1.10.ebuild | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)