as in summary, there is no mpich2 multilib which could satisfy virtual Reproducible: Always Actual Results: emerge: there are no ebuilds to satisfy "sys-cluster/mpich2[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(-)?,cxx?,fortran?,romio?,threads?]". (dependency required by "virtual/mpi-2.0-r4::gentoo" [installed]) (dependency required by "dev-libs/boost-1.62.0-r1::gentoo" [installed]) (dependency required by "app-text/libabw-0.1.1::gentoo" [installed]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument])
Christoph, did you mean to do this for mpich2 and mvapich2? Neither support multilib. commit bb66558c19112246f8577ce4ff9fb0e44bb6c6d5 Author: Christoph Junghans <junghans@gentoo.org> virtual/mpi: fixed multilib deps
(In reply to Justin Bronder from comment #1) > Christoph, did you mean to do this for mpich2 and mvapich2? Neither support > multilib. Yes, abi_x86_64(-) etc. mean assume no multilib support by default and mpich2 and mvapich2 don't have multilib support and hence they don't fulfill the boost's dependency of multilib mpi.
So what should we be doing here? Do we need to remove mvapich2 and mpich2 from the virtual?
Ah, but seems stale. $ USE=mpi emerge -pv mpich2 boost [ebuild R ] sys-cluster/mpich2-1.5::gentoo USE="cxx fortran threads -doc -mpi-threads -romio" 0 KiB [ebuild N ] virtual/mpi-2.0-r4::gentoo USE="cxx fortran threads -romio" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild R ] dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo USE="icu mpi* nls threads -context -debug -doc -python -static-libs -tools" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 python3_4 (-python3_5)" 0 KiB