ebori...@ieee.org writes: > Haven't had a chance to look into this; have you updated mpich-devel > (betas / etc), as well?
Yep. The two files are almost the same now and could even be merged into one portfile to de-duplicate logic. Same goes for openmpi{,-devel}. The noteworthy changesets are: mpi-doc: new port to abstract docs for mpich and openmpi https://smf.io/macports/changeset/2d0f20f8414b7b676f0c72079938ff3fc6dccb86 mpich_select: rename to mpi_select so all mpi ports can use it https://smf.io/macports/changeset/0946ba1629b857a1cc3ca5ae098df616c30dc2a4 mpich: use non-conflicting names for files that mpich-devel also installs https://smf.io/macports/changeset/718a0fc09fedb2c24a662e833fe286f945d30135 mpich-devel: make non-conflicting with mpich https://smf.io/macports/changeset/040299c685f3a453987bd7dadefe2882eb52bd9a openmpi: unify wrapper names as mpi{cc,cxx,fc,f77,f90} https://smf.io/macports/changeset/e6453dc62852bd9f2b6b902bb018f8bdb75d5970 _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev