> > It takes time to incorporate a new mpi implementation (and yet > > another set of awful build requirement peculiarities) into a > > a package like mine that is expected to be portable and to cope > > seamlessly with every mpi that comes along. > > What is your tool, BTW?
Well, several. Primarily ccaffeine(sandia) and babel(llnl) which are, respectively, a generic HPC component framework and the DOE language interoperability tool. > other mails today have indicated, OMPI has fully functional wrapper > compilers (mpicc, mpiCC, mpif77, mpif90) and an ompi_info command > (analogous to, but greatly superseding LAM's laminfo command). I'm looking forward to seeing how well the wrappers interact with babel+libtool. Ben
