Bug#573187: transition: mpi-defaults
Am Donnerstag, den 08.04.2010, 18:22 -0500 schrieb Pavan Balaji:
> If we choose to do the first approach, what exactly needs to change in
> the mpich2 source? It looks like this is more of a packaging issue for
> Debian?
As Lucas already said, we're already happy with what MPICH2 provides.
But thanks for your offer!
> We were having a discussion about a common ABI in the context of MPI-3.
> But that working group fizzled out. I'll check on what exactly happened
> with it in the next meeting (in May). Even if the MPI standard doesn't
> specify ABI compatibility, I'll talk to the Open MPI folks to see if
> MPICH2 and Open MPI do whatever the ABI working group was proposing
> outside of the standard, which might be sufficient for you guys.
That would be very cool indeed! I had some chat with Jeff Squyres (Open
MPI upstream) about that a while ago. Maybe you could put your heads
together on this. Having it in the standard would of course be super
cool, as it would allow to use other MPI implementations as well without
much hassle.[1]
Lucas, for this transition I will to fix the build systems, or at least
work around them. But we should get in touch after the release about
some MPI mini-policy.[2] I hope to have all patches working by the end
of the weekend, hopefully earlier.
Best regards,
Manuel
[1] Not that I'm for using proprietary stuff but I know some our users
do care for that. And so we should have that in mind. Getting to the
point where BLAS/LAPACK is (well, almost) would save us some serious
headaches. ;)
[2] There are a few more problems we do not have a solution for yet, but
getting rid of LAM and MPICH is one of the major blockers, IMHO.
Reply to: