I've just saw this entry in the wiki: https://wiki.gentoo.org/index.php?title=Multilib_System_without_emul-linux_Packages&redirect=no and decided quite quickly to jump with my two feet into it. Well, I had a few annoyances with the app-emulation/emul-linux-x86-* crufts in the past, because of using ~amd64, so the decision was easy. Now after a (very) few hours, actually it took much time to add entries in my package.env because of an ill advised switch to LTO, of compiling aproximately 110 pkgs... remains only sys-devel/gcc:4.8! Actually I had previously *only* app-emulation/emul-linux-x86-{{gtk,x}libs,opengl}. And you know what?! All that cruft was pulled by sys-devel/gcc:4.8 itself with +gcj +awt USE flags. I had to enable +gcj to be able to compile dev-java/icedtead to build mainly app-office/libreoffice; with +gtk enabled globaly, I had to enable +awt for gcc. Now, I had a single choice with that USE flags combination, actually two. Disable awt for gcc and handy pick +gtk (which will be too troublesome to keep up!), or..., remove the hundreds lines in package.use (because +abi_x86_32) and get back the emul-linux-x86-* cruft. Come on the toolchain herd... isn't anyway to remove those two following lines in toolchain.eclass?! amd64? ( multilib? ( app-emulation/emul-linux-x86-gtklibs app-emulation/emul-linux-x86-xlibs ) ) Reproducible: Always Steps to Reproduce: 1. remove emul-linux-x86-* cruft; 2. enable +abi_x86_32 to the deps of the previous emul-linux-x86 pkg; 3. emerge --deep --newuse @world; Actual Results: sys-devel/gcc:4.8[awt,gcj] pulls back app-emulation/emul-linux-x86-{{gtk,x}libs,opengl} because of the hardcoded dep in toolchain.eclass.
See also bug # 511832 . Perhaps this qualifies as a duplicate?
*** This bug has been marked as a duplicate of bug 511832 ***
