FEATURES="multilib-strict" is a critical protection by portage which helps developers keep things installed in the right place. In almost all cases this works properly and effectively. Recently things have come up which multilib-strict doesn't properly handle due to policy changes in where things are installed: https://bugs.gentoo.org/show_bug.cgi?id=424423 Even worse, a polkit which breaks multilib-strict was marked stable (I don't mean to lay blame on either side) https://bugs.gentoo.org/show_bug.cgi?id=436666 Now a valuable developer protection has been disabled and in my opinion we all suffer for it. Multiple solutions have been proposed in the above bugs, but we need to actually do something. Option 1) add RESTRICT=multilib-strict to disable the feature for ebuilds which don't support it. Personally I'm not a fan of this option as odds are high it will be abused and nothing will ever get fixed. Option 2) add a QA_MULTILIB_STRICT variable to declare exemptions I like this option much better as we can exempt specific files and when things change on a version bump we will be warned. I claim credit for niether option, however, one of these things should be implemented to deal with multilib-strict breakage while we wait for people to argue about "the proper solution"
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=55ab494c406947d67ba7d54208b4cd5e981db579 The variable is QA_MULTILIB_PATHS.
This is fixed in 2.1.11.27 and 2.2.0_alpha138.
