I've dropped mesa-10.4.2's ~amd64-fbsd keyword because it adds a new dependency on libva that isn't keyworded: media-libs/mesa/mesa-10.4.2.ebuild: DEPEND: ~amd64-fbsd(default/bsd/fbsd/amd64/9.1) ['>=x11-libs/libva-0.35.0:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] media-libs/mesa/mesa-10.4.2.ebuild: RDEPEND: ~amd64-fbsd(default/bsd/fbsd/amd64/9.1) ['>=x11-libs/libva-0.35.0:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]']
(In reply to Matt Turner from comment #0) > I've dropped mesa-10.4.2's ~amd64-fbsd keyword because it adds a new > dependency on libva that isn't keyworded: > > media-libs/mesa/mesa-10.4.2.ebuild: DEPEND: > ~amd64-fbsd(default/bsd/fbsd/amd64/9.1) > ['>=x11-libs/libva-0.35.0:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?, > abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?, > abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] > media-libs/mesa/mesa-10.4.2.ebuild: RDEPEND: > ~amd64-fbsd(default/bsd/fbsd/amd64/9.1) > ['>=x11-libs/libva-0.35.0:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?, > abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?, > abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]'] libva should be keyworded ~amd64 too I've installed mesa-11.1.0 but it required to have libva version 1.6.1 activated by ~amd64 (not tried with 1.6.0 and lower). As portage actual stable version is libva-1.3.1 mesa fails to build. Hope it helps.