Just a way to track down the packages failing this further QA test.
These issues can be catched by using: sys-devel/gcc-config -native-symlinks sys-devel/binutils-config -native-symlinks Remember that they must be also in /etc/portage/profile/package.use.force
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c7f716876fc9d0460cee1faa4935836688f3c6e commit 1c7f716876fc9d0460cee1faa4935836688f3c6e Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-08-30 07:10:07 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-08-30 07:58:20 +0000 kde-apps/yakuake: 20.04.3-r1 amd64 stable Bug: https://bugs.gentoo.org/243502 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> kde-apps/yakuake/yakuake-20.04.3-r1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
To ease debugging and fixing direct tool invocations toolchain@ created a few docs and helpers to reproduce and fix the bugs: https://wiki.gentoo.org/wiki/Project:Toolchain/use_native_symlinks The caveat is that qa@ has not yet decided what exactly this bug should be about (bug #726034).