This is an auto-filed bug because x11-libs/libdockapp 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. See also:https://projects.gentoo.org/qa/policy-guide/installed-files.html#pg0302 NOTE: If you want to change the summary, to avoid auto-filed duplicates, please at least keep the word 'static-libs'
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce6dcfc30bb8b84de9f61e729894d05131294e73 commit ce6dcfc30bb8b84de9f61e729894d05131294e73 Author: Bernard Cafarelli <voyageur@gentoo.org> AuthorDate: 2020-05-30 10:29:25 +0000 Commit: Bernard Cafarelli <voyageur@gentoo.org> CommitDate: 2020-05-30 10:29:38 +0000 x11-libs/libdockapp: add USE=static-libs Closes: https://bugs.gentoo.org/726144 Package-Manager: Portage-2.3.100, Repoman-2.3.22 Signed-off-by: Bernard Cafarelli <voyageur@gentoo.org> x11-libs/libdockapp/libdockapp-0.7.2-r3.ebuild | 49 ++++++++++++++++++++++++++ 1 file changed, 49 insertions(+)
Is static-libs really needed here? The idea is not to add this flag everywhere, but to first and foremost get rid of '.a' files.
