Could you please change the mpi? ( sys-cluster/openmpi[cxx] ) dependency into mpi? ( || ( sys-cluster/openmpi[cxx] sys-cluster/openmpi-1.2.6-r1[-nocxx] ) ) as long as sys-cluster/openmpi-1.2.6-r1 is in the tree? Would be nice for stable users who want to test newer boost versions.
*grummel* ;-) done.
mpi? ( || ( >=sys-cluster/openmpi-1.3[cxx] =sys-cluster/openmpi-1.2*[-nocxx] ) ) This does not work for the 1.2* versions of openmpi >1.2.6-r1 since they already have the cxx useflag.
this might be slightly off topic, but is there any way to fix the ebuild so that it depends on either openmpi or mpich2? I have a system dependency problem and have to use mpich2 at the moment for some regional climate models which will not work with openmpi. I've read that boost has been built using mpich2, so I think the problems can be corrected in the ebuild.
Created attachment 208309 [details, diff] Fix for MPI flag dependencies (In reply to comment #2) Now, when this boost version was stabilized portage-2.2 can't find any openmpi stable version which fulfills requirements.
Fix works for me, i.e. emerge regards openmpi-1.2.9 with use flag cxx as a valid dependency.
Can anyone fix this in portage? This issue is blocker. I have applied patch from comment #4 yesterday and updated packages successfully, but today after sync I cannot update because of this issue. stable boost-1.35.0-r5 requires >=openmpi-1.3 with cxx, but 1.3.3 is ~x86 and stable openmpi-1.2.9 uses cxx instead of required nocxx. this blocks updating. Should I make boost fix in my private portage tree or does someone fix this issue soon? Thank you very much.
BTW: ebuild for boost 1.36, 1.37, 1.39 and 1.40 uses the same incorrect dependencies. It would by very clever to change this ebuilds too for future.
Fixed in the tree, thanks.