lib-compat needs ~amd64 keyword. I have added it to my local ebuild, re-digested it, and it emerged fine. Seems to work fine as well so this should be keyworded for ~amd64, possible amd64 once aged and tested.
No it doesn't need it. http://packages.gentoo.org/search/?sstring=emul-linux-x86-compat emul-linux-x86-compat Description: emul-linux-x86 version of lib-compat, with the addition of a 32bit libgcc_s and the libstdc++ versions provided by gcc 3.3 and 3.4 for non-multilib systems.
Well it was a dep for dbbuilder which was keyword masked. But that package is shady. It also is missing the ~amd64 keyword. It installs fine but it's startup script is jacked. dbbuilder ships with allot of bundled libraries/.so which I think is bad, unless it's required? Yes it's not a needed package. But if someone wants dbbuilder on AMD64, one of the keywords needs to be added. Really I guess the dbbuilder ebuild needs to be addressed. I might just file a bug on it, since it's most likely an in-proper dep or etc in this scenario.
